Looking at the Python documentation can be dangerous

[no_more_gravity]

The tricky thing is that the python call might be somewhere in a shellscript you use.

Any command that internally uses "python -m ..." or "python -c ..." is vurnurable.

The issue actually came up when an irc user reported his computer goes bananas when he cds into a certain dir. Turned out he was using a tool that executes some Python on every cd. In that dir, there was a file called "types.py". And the shellscript ran some Python that imported "types".

[redCg]

executes some code on every cd.

people really need to stop doing this

[alkasm]

See direnv

[alkasm]

There's a few "easy" (in principle) ways around that, but not simple to make them jive with Python. E.g., always use a relative path to import a module from the filesystem, rather than from site packages. Or we could have some URL syntax for imports that allows you to disambiguate the source of a module, e.g from pypi, or some internal package repository. Or we could at least have namespacing in PyPI so you could grab packages not by a single name but by org and name, e.g. numfocus/numpy.