➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients dsamersoff, georg.brandl, rfk, terry.reedy
Date 2010-07-13.04:53:19
SpamBayes Score 0.0024035003
Marked as misclassified No
Message-id <1278996802.93.0.0349917698032.issue5950@psf.upfronthosting.co.za>
In-reply-to
Content 
>I can't imagine anyone depending on this lack-of-feature,

Neither can I, but I can imaging someone writing code that depended on the feature. If added to 3.1.3, then code that depended on it would not run on 3.1, 3.1.1, and 3.1.2. The same is true, of course, for bug fixes, but the doc does not need changing for bug fixes, and the impact is otherwise less.

> One more small incentive to make the jump to Python 3 then.

Or to 3.2 from any 3.1 version, which is the normal progession absent the dual track anomaly.
History
Date User Action Args
2010-07-13 04:53:24terry.reedysetrecipients: + terry.reedy, georg.brandl, rfk, dsamersoff
2010-07-13 04:53:22terry.reedysetmessageid: <1278996802.93.0.0349917698032.issue5950@psf.upfronthosting.co.za>
2010-07-13 04:53:21terry.reedylinkissue5950 messages
2010-07-13 04:53:19terry.reedycreate