no stack trace when using bliss as a library
looking at the following code snipplets that I ran in the python command line (NOT bliss shell):
>>> c=static.get_config()
>>> m0=c.get('m0')
>>> sdlkfaj
!!! === NameError: name 'sdlkfaj' is not defined === !!! ( for more details type cmd 'last_error' )
or
>>> c=static.get_config()
>>> s= c.get('test_session')
>>> kdsjfl
!!! === NameError: name 'kdsjfl' is not defined === !!! ( for more details type cmd 'last_error' )
we see that the stack trace is hidden even if we are not in the command line client.
Further
>>> sys.modules
>>> [x for x in sys.modules.keys() if 'ptpython' in x]
['ptpython', 'ptpython.repl', 'ptpython.python_input', 'ptpython.completer', 'ptpython.utils', 'ptpython.history_browser', 'ptpython.layout', 'ptpython.filters', 'ptpython.key_bindings', 'ptpython.prompt_style', 'ptpython.style', 'ptpython.validator', 'ptpython.eventloop', 'bliss.shell.cli.ptpython_signature_patch']
shows modules related to the command line client that are not at all to be imported when using bliss as a library.
@sebastien.petitdemange identified the https://gitlab.esrf.fr/bliss/bliss/blob/master/bliss/common/session.py#L392 to be the problem