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 vstinner
Recipients vstinner
Date 2011-01-20.01:54:53
SpamBayes Score 6.7379435e-13
Marked as misclassified No
Message-id <1295488499.02.0.313090900295.issue10952@psf.upfronthosting.co.za>
In-reply-to
Content
The Python 3 parser normalizes all identifiers using NFKC (as described in the PEP 3131). Examples:
 - U+00B5 (µ: Micro sign) is normalized to U+03BC (μ: Greek small letter mu)
 - U+FB03 (ffi: Latin small ligature ffi) is normalized to 'ffi'

The problem is that it does also normalize module names, but not the filename.

The module name in the Python source code is written with the keyboard (eg. U+00B5 in my case) and then normalized to NFKC (=> U+03BC). The filename is also written using the keyboard (U+00B5), but it is never normalized.

Attached script tests the current behaviour using "µTorrent" name with U+00B5 and U+03BC: import with U+00B5 or U+03BC use the filename with U+03BC.

The problem is that I'm able to write 'µ' (U+00B5) with my keyboard, but not U+03BC (μ).
History
Date User Action Args
2011-01-20 01:54:59vstinnersetrecipients: + vstinner
2011-01-20 01:54:59vstinnersetmessageid: <1295488499.02.0.313090900295.issue10952@psf.upfronthosting.co.za>
2011-01-20 01:54:54vstinnerlinkissue10952 messages
2011-01-20 01:54:54vstinnercreate