On this page
libtmux.exc.MultipleObjectsReturned
- Module
- libtmux.exc
- Package
- libtmux
- Source
- src/libtmux/exc.py
- Bases:
A lookup expected one object and matched several.
Raised by
get. UnlikeObjectDoesNotExist, adefaultdoes **not** suppress it: adefaultis a stand-in for an object that is *absent*, and an ambiguous lookup is not an absent one. Silently answering with one of several equally valid matches is how you end up driving the wrong pane.On a server-wide collection, several matches for a single id is ordinary and means the window is linked into more than one session. See winlinks for what to do about it.
Examples
>>> from libtmux import exc >>> str(exc.MultipleObjectsReturned()) 'Multiple objects returned'A lookup that matched too much reports how much, and for what:
>>> str(exc.MultipleObjectsReturned(count=2, query={"pane_id": "%0"})) "Multiple objects returned (2): pane_id='%0'"It is part of the
LibTmuxExceptionhierarchy, soexcept LibTmuxExceptioncatches it:>>> issubclass(exc.MultipleObjectsReturned, exc.LibTmuxException) TrueDiscussed in Filtering and queries
1 declared, 1 inherited
Members
- __init__ method
Inherited members
Reached through libtmux.exc.LibTmuxException.
- __str__ libtmux.exc.LibTmuxException Render with optional
"<subcommand>: …"prefix.