You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For pure python bv_maker modules, there is a special configuration code that make sure that the Python source of each component is in sys.path. It rely on a file python/sitecustomize/bv_maker_pure_python.pth located in the build directory. Each component code is independent and just make sure that its source directory is in this file. But this file is never cleared, therefore directories put here once are here forever. Moreover, directories are added at the end. Thus older directories are first in the list.
The text was updated successfully, but these errors were encountered:
Re-activate this issue is a good moment to think about this bv_maker_pure_python.pth file. I will try to see if it is possible to replace it by using pip install -e. A priori, it does not seem too difficult now that we have casa-distro.
Author Name: Cointepas, Yann (@sapetnioc)
Original Redmine Issue: 12733, https://bioproj.extra.cea.fr/redmine/issues/12733
Original Date: 2015-06-11
Original Assignee: Cointepas, Yann
For pure python bv_maker modules, there is a special configuration code that make sure that the Python source of each component is in sys.path. It rely on a file python/sitecustomize/bv_maker_pure_python.pth located in the build directory. Each component code is independent and just make sure that its source directory is in this file. But this file is never cleared, therefore directories put here once are here forever. Moreover, directories are added at the end. Thus older directories are first in the list.
The text was updated successfully, but these errors were encountered: