search

BCDA-APS / use_bluesky

Tools to help APS use the Bluesky Framework (https://blueskyproject.io/)
8 stars 3 forks source link

Warnings thrown during use_bluesky/IPython exit #24

Closed mdwyman closed 6 years ago

mdwyman commented 7 years ago

@tcaswell, @danielballan

When exiting IPython (simply using "exit") after a Bluesky session (which was started with use_bluesky.sh), many copies of the following warning are shown:

Traceback (most recent call last): File "/home/mwyman/Apps/BlueSky/lib/python3.6/site-packages/epics/ca.py", line 251, in initialize_libca File "/home/mwyman/Apps/BlueSky/lib/python3.6/site-packages/epics/ca.py", line 213, in find_libCom File "/home/mwyman/Apps/BlueSky/lib/python3.6/site-packages/epics/ca.py", line 178, in _find_lib File "/home/mwyman/Apps/BlueSky/lib/python3.6/ctypes/util.py", line 302, in find_library File "/home/mwyman/Apps/BlueSky/lib/python3.6/ctypes/util.py", line 249, in _findSoname_ldconfig ImportError: sys.meta_path is None, Python is likely shutting down

Is this related to MonitorDispatcher thread running (but not stopped) at exit? Is there a cleaner way to exit?

Thanks, Max

danielballan commented 7 years ago

That is the standard way to exit and, if everything goes as planned, IPython should exit cleanly without a traceback like this. Is this function run as part of your IPython profile? I might need more context from @prjemian to know what to look for here.

P.S. You're looking for @tacaswell -- missing the A.

tacaswell commented 7 years ago

This may also be a pyepics bug, see https://github.com/pyepics/pyepics/issues/89 and https://github.com/pyepics/pyepics/pull/102

Should be fixed in the latest version of pyepics.

prjemian commented 7 years ago

We do run the setup() function. I've seen this on a couple computers. Up to now, been ignoring it as "exit comments". There may be a way to quiet them. I'll check those two PyEpics issues and our version number.

prjemian commented 6 years ago

not seeing this, closing (open new if seen again)