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, amaury.forgeotdarc, benjamin.peterson, brett.cannon, eric.araujo, georg.brandl, r.david.murray, terry.reedy, vstinner
Date 2011-01-08.06:23:10
SpamBayes Score 3.489664e-10
Marked as misclassified No
Message-id <1294467792.31.0.565393392221.issue3080@psf.upfronthosting.co.za>
In-reply-to
Content
If I edit a file with IDLE, save it, and successfully run it (perhaps to test it), then when I edit a second file that imports the first, I expect the import to work. It does not always (see #10828).

Import is part of the core definition of the language. Unicode identifiers are supposedly part of Python3. Given the existence of <identifier>.py in the current directory, 'import identifier' should work. If it does not, the 3.1 message '<identifier> not found' is more truthful than the current 'no module named <identifier>', when there is one.

The doc says "identifier ::= (identifier ".")* identifier". As long as that is not true, some indication of the restriction that most people can understand would be nice. (And I suspect that a majority of Windows users, at least in the US, have no idea of what an 'ANSI code page' is.)
History
Date User Action Args
2011-01-08 06:23:12terry.reedysetrecipients: + terry.reedy, brett.cannon, georg.brandl, amaury.forgeotdarc, vstinner, benjamin.peterson, eric.araujo, Arfrever, r.david.murray
2011-01-08 06:23:12terry.reedysetmessageid: <1294467792.31.0.565393392221.issue3080@psf.upfronthosting.co.za>
2011-01-08 06:23:10terry.reedylinkissue3080 messages
2011-01-08 06:23:10terry.reedycreate