[issue15710] logging module crashes in Python 2.7.3 for handler.setLevel(long)

Roundup Robot added the comment: New changeset 8ba6d8fc9740 by Vinay Sajip in branch '2.7': Closes #15710: accept long in _checkLevel. http://hg.python.org/cpython/rev/8ba6d8fc9740 -- nosy: +python-dev resolution: invalid -> fixed stage: -> committed/rejected status: open -> closed ___

[issue15710] logging module crashes in Python 2.7.3 for handler.setLevel(long)

Vinay Sajip added the comment: It's not that big a deal, and doesn't matter for 3.x anyway. It just doesn't seem quite right, so I'll make the change soon. -- ___ Python tracker ___

[issue15710] logging module crashes in Python 2.7.3 for handler.setLevel(long)

Antoine Pitrou added the comment: > type(-2**31) is long for 2.5 and 2.6 as well as 2.7. The check was > added as a response to #6314, to catch incorrect values being passed > as levels. Well, what is an incorrect value and why would you bother refusing long? And how about small long values (e.g

[issue15710] logging module crashes in Python 2.7.3 for handler.setLevel(long)

Vinay Sajip added the comment: type(-2**31) is long for 2.5 and 2.6 as well as 2.7. The check was added as a response to #6314, to catch incorrect values being passed as levels. It could be argued that -2**31 is not a sensible log level. While int and long are supposed to be interchangeable fo

[issue15710] logging module crashes in Python 2.7.3 for handler.setLevel(long)

Antoine Pitrou added the comment: This seems to miss the point that it's a regression. int and long are supposed to be interchangeable for most purposes. -- nosy: +pitrou status: pending -> open ___ Python tracker

[issue15710] logging module crashes in Python 2.7.3 for handler.setLevel(long)

Vinay Sajip added the comment: I don't feel it would be correct to allow long for log levels, since a log level is not intended to have that range. It would be more sensible to get the ESAPI developers to use a more appropriate boundary value; in general, negative log values are not used (they

[issue15710] logging module crashes in Python 2.7.3 for handler.setLevel(long)

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue15710] logging module crashes in Python 2.7.3 for handler.setLevel(long)

Changes by Antoine Pitrou : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue15710] logging module crashes in Python 2.7.3 for handler.setLevel(long)

New submission from Tobin Baker: I'm using a 3rd-party library (ESAPI) which defines a log level as the literal -2**31. This worked fine until I upgraded to Python 2.7.3, which, unlike all previous versions of Python, coerces that literal to long rather than int. The following code in the logg