Re: [Python-Dev] Issue 4195: Can't execute packages with -m in Python 2.6/3.0

I don't think that removing an unintentional and subtly broken feature is a regression. On Fri, Nov 21, 2008 at 7:04 PM, Lisandro Dalcin <[EMAIL PROTECTED]> wrote: > Unless this is considered a regression... > > On Tue, Nov 18, 2008 at 12:51 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote: >> I thi

Re: [Python-Dev] Issue 4195: Can't execute packages with -m in Python 2.6/3.0

Unless this is considered a regression... On Tue, Nov 18, 2008 at 12:51 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > I think it crosses the line. > > On Tue, Nov 18, 2008 at 2:55 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote: >> I need a release manager call on whether or not the proposed resolu

Re: [Python-Dev] Issue 4195: Can't execute packages with -m in Python 2.6/3.0

I think it crosses the line. On Tue, Nov 18, 2008 at 2:55 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote: > I need a release manager call on whether or not the proposed resolution > of this issue goes beyond what is acceptable for a bug fix in 2.6.1. > > Short version: > - Python 2.5 allowed packages

[Python-Dev] Issue 4195: Can't execute packages with -m in Python 2.6/3.0

I need a release manager call on whether or not the proposed resolution of this issue goes beyond what is acceptable for a bug fix in 2.6.1. Short version: - Python 2.5 allowed packages to be executed with -m, but in a broken way - I disabled the broken way for 2.6, but didn't provide a replacemen