28 Feb
2021
28 Feb
'21
11:26 p.m.
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.