A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2013-December/130736.html below:

[Python-Dev] cpython (3.3): Issue #17576: Deprecation warning emitted now when __int__() or __index__()

[Python-Dev] cpython (3.3): Issue #17576: Deprecation warning emitted now when __int__() or __index__() [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 
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.
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4