Home Original page

[Python-Dev] Backwards Incompatibility in logging module in 3.4?

Nick Coghlan ncoghlan at gmail.com
Fri Jun 13 01:10:16 CEST 2014 
On 13 Jun 2014 08:59, "Don Spaulding" <donspauldingii at gmail.com> wrote:
>
> Hi there,
>
> I just started testing a project of mine on Python 3.4.0b1.  I ran into a
change that broke compatibility with the logging module in 3.3.
>
> The basic test is:
>
>     $ py34/bin/python -c 'import logging;
print(logging.getLevelName("debug".upper()))'
>     Level DEBUG
>
>     $ py33/bin/python -c 'import logging;
print(logging.getLevelName("debug".upper()))'
>     10
>
> I quickly stumbled upon this webpage:
>
> http://aazza.github.io/2014/05/31/testing-on-multiple-versions-of-Python/
>
> Which led me to this ticket regarding the change:
>
> http://bugs.python.org/issue18046
>
> Is this a bug or an intentional break?  If it's the latter, shouldn't
this at least be mentioned in the "What's new in Python 3.4" document?  If
it's the former, should I file a bug?

Yes, it sounds like a bug to me - there's no indication of an intent to
change behaviour with that cleanup patch.

Cheers,
Nick.


>
> Thanks,
> Don
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20140613/61e52060/attachment.html>
More information about the Python-Dev mailing list