New submission from Jan Kratochvil jan.kratoch...@redhat.com:
People use custom Python builds setting PYTHONHOME and PYTHONPATH to these
custom builds. This may be expected to break running system Python binary but
it also unexpectedly breaks various applications which also embed Python:
$
Éric Araujo mer...@netwok.org added the comment:
An alternate idea would be to recommend more strongly in the doc that people
should not shadow standard library module names (in your example, site).
--
nosy: +eric.araujo
___
Python tracker
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +brett.cannon, ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14956
___
___
Jan Kratochvil jan.kratoch...@redhat.com added the comment:
This site.py is only an example how it can happen. In reality it is due to .py
files intended for incompatible version of Python. I am not a Python
programmer to have some appropriate incompatible code at hand.
--
Éric Araujo mer...@netwok.org added the comment:
This site.py is only an example how it can happen.
site is special, as it’s one of the modules imported during Python startup.
Can you reproduce the bug with the same file named os.py? (I expect you can.)
Can you reproduce with spam.py? (I
