homepage

Importlib doesn't cover case-insensitivity on file extensions under Windows (see test.test_import.test_import: http://www.python.org/dev/buildbot/all/builders/x86%20XP-5%203.x/builds/41/steps/test/logs/stdio). Should add a test to test_importlib and then fix (but only for Windows; apparently this isn't honoured under OS X even though it is case-insensitive).

OK, is supporting this really necessary? It's a special case on Windows only; even OS X which is also case-insensitive doesn't support this.
But if it does need to be supported, then does someone know if this extends to all module types or only .py and .pyw files (e.g. do .pyc files need this along with extension modules)? If there is no special-casing to that extent then _PathFinder.find_module() will need to cache all files with lowercase file extensions no matter what PYTHONCASEOK says on Windows. That way the performance is only costly at cache building time and there is no expensive checking for all other OSs.

New changeset a32be109bd86 by Brett Cannon in branch 'default':
Issue #14581: Windows users are allowed to import modules w/o taking
http://hg.python.org/cpython/rev/a32be109bd86 

http://www.python.org/dev/buildbot/all/builders/x86%20XP-5%203.x/builds/98/steps/test/logs/stdio suggests this fix worked.