[issue10263] "python -m site" does not print path details
Ned Deily
report at bugs.python.org
Mon Nov 1 19:03:10 CET 2010
Ned Deily <nad at acm.org> added the comment:
Nick is the authority on -m so perhaps he can confirm this but I believe the execution of -m is carried out by the runpy standard library module and the runpy module essentially goes through the process of finding a module from scratch by searching through the modules in sys.path, thus bypassing the altered sys.path which the setuptools/Distribute site module "bootstrapped" and removed itself from. So runpy will always find the setuptools/Distribute site module first since it is first on sys.path (until it executes and removes itself from sys.path). It seems you've found one case where the sys.path manipulations of setuptools/Distributes make a difference: when trying to run site itself. You can see which site module is found by runpy by trying:
import runpy
runpy.run_module("site")
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10263>
_______________________________________
More information about the Python-bugs-list
mailing list