[issue4211] frozen packages set an improper __path__ value

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Fixed in r67112. -- nosy: +benjamin.peterson resolution: accepted -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> __

[issue4211] frozen packages set an improper __path__ value

Guido van Rossum <[EMAIL PROTECTED]> added the comment: I approve of the API change. It's 3.0, dammit! -- nosy: +gvanrossum resolution: -> accepted ___ Python tracker <[EMAIL PROTECTED]>

[issue4211] frozen packages set an improper __path__ value

Nick Coghlan <[EMAIL PROTECTED]> added the comment: FWIW, I agree with the idea of fixing it for 3.0 and leaving it in for 2.x. -- nosy: +ncoghlan ___ Python tracker <[EMAIL PROTECTED]> __

[issue4211] frozen packages set an improper __path__ value

Changes by Brett Cannon <[EMAIL PROTECTED]>: -- stage: -> commit review ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list

[issue4211] frozen packages set an improper __path__ value

Brett Cannon <[EMAIL PROTECTED]> added the comment: I have an attached patch that fixes the reported problem. First, it adds a sanity check that no empty module name is checked for (crashes the interpreter otherwise). Second, the __path__ attribute is now a list. This does break backwards-compa

[issue4211] frozen packages set an improper __path__ value

Brett Cannon <[EMAIL PROTECTED]> added the comment: Looking at Python/import.c:find_module, fixing this will require changing the setting of __path__ for frozen packages and how frozen modules are found. The former will require changing PyImport_ImportFrozenModule() to use a list instead of a str

[issue4211] frozen packages set an improper __path__ value

New submission from Brett Cannon <[EMAIL PROTECTED]>: If you import a frozen package (e.g. __phello__), __path__ is set to '__phello__'. But this should be a list as specified by both PEP 302 (http://www.python.org/dev/peps/pep-0302/) and the original doc outlining the package mechanism (http://w