[Python-Dev] Issue10271 - warnings.showwarning should allow any callable object (original) (raw)
Terry Reedy tjreedy at udel.edu
Thu Jul 21 20:49:47 CEST 2011
- Previous message: [Python-Dev] Issue10271 - warnings.showwarning should allow any callable object - request commiter
- Next message: [Python-Dev] Latest draft of PEP 399 (Pure Python/C Accelerator Module Compatibility Requirements)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 7/21/2011 2:15 PM, Brett Cannon wrote:
It won't break any existing code, but it could cause compatibility for future code. Imagine I wrote some code for 3.2.2 where this change was backported and worked only with this fix. That would mean my code would fail in any Python 3.2.1 or older interpreter. That's simply not acceptable as that means that code would be magically busted for some versions of Python 3.2 but not all of them.
In other words, Python 3.2 is a fixed language, cpython3.2.z's are intended to be increasingly better implementations of that language, although regressions can and do happen (as with issue 12540).
-- Terry Jan Reedy
- Previous message: [Python-Dev] Issue10271 - warnings.showwarning should allow any callable object - request commiter
- Next message: [Python-Dev] Latest draft of PEP 399 (Pure Python/C Accelerator Module Compatibility Requirements)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]