On Monday, September 27, 2021 at 12:46:30 PM UTC-7 Nils Bruin wrote: > I noticed: > > $ sage --python3 -c "import sys; print(sys.path)" ['', > '/usr/lib64/python39.zip', '/usr/lib64/python3.9', > '/usr/lib64/python3.9/lib-dynload', > '/usr/local/sage/sage-git/local/lib64/python3.9/site-packages', > '/usr/local/sage/sage-git/local/lib/python3.9/site-packages'] > > note that the first enstries in this list actually refer to the system > python, not the sage python! I think that means that any patched package > installs that sage uses will be shadowed by the system installations. >
No, that's not how it works. Sage uses a venv over the system python. The first items in the list provide access to python's standard library. System-installed packages would be found in a directory like /usr/lib64/python3.9/site-packages. Our venv is configured so that it does not provide access to system packages, which is why you don't see this directory in the path. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/2b0e4dc9-2664-484d-8131-1e270657cd35n%40googlegroups.com.
