Nick Coghlan [EMAIL PROTECTED] added the comment:
Now, if someone was to provide a 2.7 rfe with associated patch that
implements this feature properly, and includes an explanation for why it
doesn't subtly break imports the way 2.5 does, that would be a
completely different story.
But it isn't
Richard Jones [EMAIL PROTECTED] added the comment:
I'm afraid it's all a bit opaque to an outsider like me. I've no idea
what subtle breakage the feature was causing. I just saw it working
quite nicely for me in 2.5 :)
___
Python tracker [EMAIL PROTECTED]
Nick Coghlan [EMAIL PROTECTED] added the comment:
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
Changes by Georg Brandl [EMAIL PROTECTED]:
--
assignee: - ncoghlan
nosy: +ncoghlan
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3441
___
___
New submission from Richard Jones [EMAIL PROTECTED]:
The Python 2.5 -m command-line option allowed execution of a package
directly, by invoking the __init__.py module.
Python 2.6 no longer allows this.
This is a quite unfortunate regression, and I would urge the decision to
hobble it to be
Changes by Richard Jones [EMAIL PROTECTED]:
--
type: - behavior
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3441
___
___
Python-bugs-list mailing
