Re: [Python-Dev] cpython (3.3): Issue #17576: Deprecation warning emitted now when __int__() or __index__()
Am 12.12.2013 16:22, schrieb R. David Murray: > On Thu, 12 Dec 2013 10:54:05 +0200, Serhiy Storchaka > wrote: >> 12.12.13 00:24, Antoine Pitrou МапО�ав(ла): >> > On Wed, 11 Dec 2013 20:28:19 +0100 (CET) >> > serhiy.storchaka wrote: >> >> http://hg.python.org/cpython/rev/618cca51a27e >> >> changeset: 87899:618cca51a27e >> >> branch: 3.3 >> >> parent: 87896:46186736e91c >> >> user:Serhiy Storchaka >> >> 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? >> >> Some clarifications. This is a precursor of a bugfix. I split a patch on >> two parts for simplicity. First part doesn't change behavior besides >> introducing warnings. Second part is simple and will change behavior (I >> still doubt how many behavior it should change). > > That doesn't address the question of why the deprecation is added > to a bug-fix release. Normal policy is deprecate in the current > feature release and make the change in the next feature release. > > Is there a reason why the normal deprecation process should not be > followed in this case? It being a not-likely-to-be-encountered > in-the-real-world bug could be one such reason, if the release > managers agree. I don't think it's useful to add the warning (although it won't break anything). Deprecations should be treated like features: their status should only change in a minor (3.x.0) release. Now the second part (changing behavior) also sounds potentially dangerous :) Georg ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Summary of Python tracker Issues
ACTIVITY SUMMARY (2013-12-13 - 2013-12-20)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open4323 ( +1)
closed 27484 (+56)
total 31807 (+57)
Open issues with patches: 1980
Issues opened (44)
==
#18283: shutil.which() should support bytes
http://bugs.python.org/issue18283 reopened by haypo
#19766: test_venv: test_with_pip() failed on "AMD64 Fedora without thr
http://bugs.python.org/issue19766 reopened by ncoghlan
#19967: asyncio: remove _TracebackLogger
http://bugs.python.org/issue19967 reopened by pitrou
#19979: Missing nested scope vars in class scope (bis)
http://bugs.python.org/issue19979 opened by arigo
#19980: Improve help('non-topic') response
http://bugs.python.org/issue19980 opened by terry.reedy
#19982: Add a "target" parameter to runpy.run_path and runpy.run_modul
http://bugs.python.org/issue19982 opened by ncoghlan
#19983: Ctrl-C at startup can end in a Py_FatalError call
http://bugs.python.org/issue19983 opened by Jurko.GospodnetiÄ
#19984: Add new format of fixed length string for PyErr_Format
http://bugs.python.org/issue19984 opened by vajrasky
#19985: Not so correct error message when initializing Struct with ill
http://bugs.python.org/issue19985 opened by vajrasky
#19989: Error while sending function code over queue (multiprocessing)
http://bugs.python.org/issue19989 opened by Filip.Malczak
#19990: Add unittests for imghdr module
http://bugs.python.org/issue19990 opened by Claudiu.Popa
#19991: configparser instances cannot be pretty printed
http://bugs.python.org/issue19991 opened by Andrei.Kucharavy
#19992: subprocess documentation not explicit about fileno()
http://bugs.python.org/issue19992 opened by Thayne.McCombs
#19993: Pool.imap doesn't work as advertised
http://bugs.python.org/issue19993 opened by jneb
#19995: hex() and %x, oct() and %o do not behave the same
http://bugs.python.org/issue19995 opened by ethan.furman
#19996: httplib infinite read on invalid header
http://bugs.python.org/issue19996 opened by Lukasa
#19997: imghdr.what doesn't accept bytes paths
http://bugs.python.org/issue19997 opened by Claudiu.Popa
#19998: Python 2.7.6 fails to build _ctypes on GCC 2.x toolchain
http://bugs.python.org/issue19998 opened by jamercee
#2: SSLContext.get_ca_certs() and self-signed certs
http://bugs.python.org/issue2 opened by christian.heimes
#20001: pathlib inheritance diagram too large
http://bugs.python.org/issue20001 opened by pitrou
#20002: Cleanup and microoptimize pathlib
http://bugs.python.org/issue20002 opened by serhiy.storchaka
#20003: Language Ref "raise" doc misssing "from None"
http://bugs.python.org/issue20003 opened by rurpy2
#20008: Clean up/refactor/make discoverable test_decimal
http://bugs.python.org/issue20008 opened by zach.ware
#20009: Property should expose wrapped function.
http://bugs.python.org/issue20009 opened by hardkrash
#20010: time.strftime('%z') didn't make +HHMM return in windows xp
http://bugs.python.org/issue20010 opened by civalin
#20011: Changing the signature for Parameter's constructor
http://bugs.python.org/issue20011 opened by Antony.Lee
#20012: Re: Allow Path.relative_to() to accept non-ancestor paths
http://bugs.python.org/issue20012 opened by javawizard
#20013: imaplib behaviour when deleting selected folder
http://bugs.python.org/issue20013 opened by dveeden
#20014: Makes array.array constructor accepts ascii-unicode typecode
http://bugs.python.org/issue20014 opened by vajrasky
#20015: Allow 1-character ASCII unicode where 1-character str is requi
http://bugs.python.org/issue20015 opened by serhiy.storchaka
#20020: "modernize" the modulefinder module
http://bugs.python.org/issue20020 opened by eric.snow
#20021: "modernize" makeopcodetargets.py
http://bugs.python.org/issue20021 opened by eric.snow
#20022: "modernize" the Mac bundlebuilder.py script
http://bugs.python.org/issue20022 opened by eric.snow
#20024: Py_BuildValue() can call Python code with an exception set
http://bugs.python.org/issue20024 opened by haypo
#20026: sqlite: handle correctly invalid isolation_level
http://bugs.python.org/issue20026 opened by haypo
#20027: Fixed support for Indian locales
http://bugs.python.org/issue20027 opened by serhiy.storchaka
#20028: Confusing error message when giving invalid quotechar in initi
http://bugs.python.org/issue20028 opened by vajrasky
#20029: asyncio.SubprocessProtocol is missing
http://bugs.python.org/issue20029 opened by akira
#20030: unittest.TestLoader.discover return value incorrectly document
http://bugs.python.org/issue20030 opened by arnaut-billings
#20031: unittest.TextTestRunner missing run() documentation.
http://bugs.python.org/issue20031 opened by arnaut-billings
#20032: asyncio.Future.set_exception() creates a reference cycle
http://bugs.python.org/issue20032 opened by haypo
