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 ncoghlan, roger.serwy, terry.reedy
Date 2013-06-27.20:21:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In a commiters-list discussion of heuristics for what patches can go into non-Idle 2.7, Nick Coghlan offered "simplifying cross-version maintenance". (He also mentioned "addressing issues that arise due to changes in the underlying platforms", which is another issue I will open.)

Because of PEP 434 and the subsequent application of most Idle patches to all current versions, cross-version consistency is even more important for idlelib than the rest of the repository. When backporting patches, both context and changed lines must match. My experience so far is that merge conflicts are normal. So I think the latitude for consistency patches to reduce these should be even wider than for the rest of the repository. On the other hand, the current lack of tests suggests more caution than for the rest of the repository. 

For this issue, I would like to at least change "except exception, e:" to "except exception as e:". This is about as safe as anything, and grepping 2.7 idlelib for "except .*, *." yields 23 hits where the ',' is not for multiple exceptions.

2.7 has about 80 print statements. While I would not change all in one patch (maybe 4), all in any file should be changed together when the future import is added at the top. Once this is done, forgetting to add parens or convert '>> file' results in a SyntaxError. So this is also pretty safe if the file compiles.

Current uses of int() seem to be for str or float conversion, not a/b truncations. That is already done with a//b.

There do not seem to be any unicode string literals.

Have I forgotten any generic ways to make 2.7 code the same as 3.x?
Date User Action Args
2013-06-27 20:21:36terry.reedysetrecipients: + terry.reedy, ncoghlan, roger.serwy
2013-06-27 20:21:36terry.reedysetmessageid: <>
2013-06-27 20:21:36terry.reedylinkissue18316 messages
2013-06-27 20:21:36terry.reedycreate