[issue14052] importlib mixes up '.' and os.getcwd()

Stefan Krah added the comment: It just happened again on the new FreeBSD-9.0 bot: http://www.python.org/dev/buildbot/all/builders/AMD64%20FreeBSD%208.2%203.x/builds/1845/steps/test/logs/stdio == FAIL: test_package___file__ (te

[issue14052] importlib mixes up '.' and os.getcwd()

Changes by Brett Cannon : -- resolution: -> invalid status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue14052] importlib mixes up '.' and os.getcwd()

Brett Cannon added the comment: The test suite does use importlib for some imports as finders from importlib for some packages stick around. I brought this up a way back but people thought it was actually a good idea to let importlib handle imports to stress test it. Anyway, if it can't be re

[issue14052] importlib mixes up '.' and os.getcwd()

Antoine Pitrou added the comment: [...] And I can't reproduce, even when using --randseed. -- ___ Python tracker ___ ___ Python-bugs

[issue14052] importlib mixes up '.' and os.getcwd()

Antoine Pitrou added the comment: There was the following sporadic buildbot failure: == FAIL: test_package___file__ (test.test_imp.PEP3147Tests) -- Traceback

[issue14052] importlib mixes up '.' and os.getcwd()

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue14052] importlib mixes up '.' and os.getcwd()

Nick Coghlan added the comment: Purging __file__ of relative references isn't a problem - they're *supposed* to always be absolute. The import.c version just stuffs it up sometimes (mainly due to the way it handles the empty string in the path). IOW, while the importlib behaviour *is* differe

[issue14052] importlib mixes up '.' and os.getcwd()

Changes by Éric Araujo : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue14052] importlib mixes up '.' and os.getcwd()

Brett Cannon added the comment: It's surprisingly difficult to get right because tests will fail if you keep the path relative in other situations (such as test_cmd_line_script). It was an absolute pain to get it to where it is now. If you can make it keep the relative path and pass the test

[issue14052] importlib mixes up '.' and os.getcwd()

New submission from Antoine Pitrou : An empty sys.path string means the current directory in relative terms: $ touch foo.py $ python3 -c "import foo; print(foo.__file__)" foo.py But importlib uses os.getcwd() instead in PathFinder._path_importer_cache(). This impacts semantics of path searchi