[Python-Dev] PEP 385 progress report (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Sat Feb 13 08:55:36 CET 2010
- Previous message: [Python-Dev] PEP 385 progress report
- Next message: [Python-Dev] PEP 385 progress report
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Benjamin Peterson wrote:
2010/2/12 Nick Coghlan <ncoghlan at gmail.com>:
Of course, PEP 291 could do with a list of 2.5 and 2.6 specific features first... I think that section is rather pointless to keep updated, since a good list can be found in the what's new documents. What people really need to do is run the unittests on all supported versions.
It's handy as a list of big ticket items to avoid, especially those that can significantly affect the way you structure code.
Agreed that the main enforcement should be to run those tests on the relevant older versions.
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] PEP 385 progress report
- Next message: [Python-Dev] PEP 385 progress report
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]