New submission from Kristján Valur Jónsson:
When .py files are assembled into a directory structure using direct symbolic
links to the files, something odd happens to sys.path[0].
Consider this file structure:
/pystuff/
foo.py - /scripts/foo.py
bar.py - /libs/bar.py
foo.py contains the
Kristján Valur Jónsson added the comment:
btw, this is the opposite issue to issue #1387483
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17639
___
Nick Coghlan added the comment:
Adding Guido Ned, as my recollection is that some of the weirdness in the
sys.path[0] symlink resolution was to placate the test suite on Mac OS X (at
least, that was a cause of failures in the initial runpy module implementation
until Guido tracked down the
Changes by Ralf Schmitt python-b...@systemexit.de:
--
nosy: +schmir
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17639
___
___
Python-bugs-list
