[Python-Dev] 2.5 and beyond
Anthony Baxter
anthony at interlink.com.au
Sat Jul 1 10:02:21 CEST 2006
On Saturday 01 July 2006 05:19, Martin v. Löwis wrote:
> James Y Knight wrote:
> > I just submitted http://python.org/sf/1515169 for the
> > ImportWarning issue previously discussed here. IMO it's
> > important.
>
> At the moment (i.e. without an acceptable alternative
> implementation) it's primarily a policy issue. There really isn't
> any bug here; (to speak with Microsoft's words): This behavior is
> by design.
>
> Only the release manager or the BDFL could revert the feature, and
> Guido already stated that the warning stays until Python 3, and
> probably even after that. I personally believe the only chance to
> get this changed now is a well-designed alternative implementation
> (although this is no promise that such an alternative would
> actually be accepted).
given the number of people and ways that this can emit a spurious
warning, I think it should be reverted for 2.5. At _best_ we could
maybe have a new -W switch to make it be generated, but this should
be off by default.
Anthony
--
Anthony Baxter <anthony at interlink.com.au>
It's never too late to have a happy childhood.
More information about the Python-Dev
mailing list