This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients Arfrever, docs@python, eric.araujo, eric.snow, r.david.murray, shai, terry.reedy
Date 2013-02-09.00:46:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I looked through both the old 2.7 import statement doc and the new 3.3 import statement doc and import system chapter (5. The import system) and could not find anything about what a Path Based Finder path entry finder does when a particular path entry has multiple candidates (a directory, a file.pyx, and __pycache__/*.pyc entries are all possible).

I also notices that there is no (longer a) description of the simple default search for default installations: sys.modules, builtin modules, and sys.path directories. Up to here, first found rules. If there were such a simplified description, it could be followed by a description of resolution of conflicts within a sys.path directory.
Date User Action Args
2013-02-09 00:46:57terry.reedysetrecipients: + terry.reedy, eric.araujo, Arfrever, r.david.murray, docs@python, eric.snow, shai
2013-02-09 00:46:57terry.reedysetmessageid: <>
2013-02-09 00:46:57terry.reedylinkissue17108 messages
2013-02-09 00:46:57terry.reedycreate