[Python-Dev] cpython (3.3): Issue #17576: Deprecation warning emitted now when __int__() or __index__()
Antoine Pitrou
solipsis at pitrou.net
Wed Dec 11 23:24:47 CET 2013
More information about the Python-Dev mailing list
Wed Dec 11 23:24:47 CET 2013
- Previous message: [Python-Dev] [buildbot] Increase number of stored builds
- Next message: [Python-Dev] cpython (3.3): Issue #17576: Deprecation warning emitted now when __int__() or __index__()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 11 Dec 2013 20:28:19 +0100 (CET) serhiy.storchaka <python-checkins at python.org> wrote: > http://hg.python.org/cpython/rev/618cca51a27e > changeset: 87899:618cca51a27e > branch: 3.3 > parent: 87896:46186736e91c > user: Serhiy Storchaka <storchaka at gmail.com> > date: Wed Dec 11 21:07:54 2013 +0200 > summary: > Issue #17576: Deprecation warning emitted now when __int__() or __index__() > return not int instance. Introduced _PyLong_FromNbInt() and refactored > PyLong_As*() functions. Is it ok to add deprecation warnings in bugfix versions? Regards Antoine.
- Previous message: [Python-Dev] [buildbot] Increase number of stored builds
- Next message: [Python-Dev] cpython (3.3): Issue #17576: Deprecation warning emitted now when __int__() or __index__()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list