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 ncoghlan
Recipients benjamin.peterson, ncoghlan, richard
Date 2008-07-26.07:10:36
SpamBayes Score 0.00206198
Marked as misclassified No
Message-id <1217056237.72.0.910007059965.issue3441@psf.upfronthosting.co.za>
In-reply-to
Content
If I recall correctly (it's been a while), the breakages were tied in
with relative imports - probably something like explicit relative
imports not working at all, and implicit relative imports appearing to
work, but resulting in incorrect module names and sys.modules entries
(similar to running a file from inside a package directly).

Doing "python -m package.__init__" instead of "python -m package" is
actually better behaved (although still a little odd - the
__init__ module code gets run once on the actual package import, and
then again as __main__).
History
Date User Action Args
2008-07-26 07:10:38ncoghlansetspambayes_score: 0.00206198 -> 0.00206198
recipients: + ncoghlan, richard, benjamin.peterson
2008-07-26 07:10:37ncoghlansetspambayes_score: 0.00206198 -> 0.00206198
messageid: <1217056237.72.0.910007059965.issue3441@psf.upfronthosting.co.za>
2008-07-26 07:10:37ncoghlanlinkissue3441 messages
2008-07-26 07:10:36ncoghlancreate