> And unlike a venv, "python -m" doesn't let you ensure > that the code executed is the version installed in user site-packages
I have had enough problems with this that when I do modify/replace something, I put in a marker that I can check for explicitly. Expecting this marker to run automatically at import (and the results not to be swallowed) turned out to be insufficient. > it could be coming from a directory earlier in sys.path. The obvious solution is to put the current directory in front of sys.path. Alas, security folks didn't like that idea. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/M3U72J6OR53LF5REA7LOZBIQUUXXHV65/ Code of Conduct: http://python.org/psf/codeofconduct/
