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 Todd.Rovito, asvetlov, ned.deily, roger.serwy, terry.reedy
Date 2013-06-06.18:29:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1370543391.75.0.919797325796.issue18152@psf.upfronthosting.co.za>
In-reply-to
Content
Backporting Idle patches from 3.x to 2.7 would be easier with a canned edit script. Below are the substitutions I can think of immediately. Do any of you know of others?

Easy (str.replace):
tkinter -> Tkinter
import tkinter.messagebox as tkMessageBox -> import tkMessageBox

A bit tricky (but still use str.replace):
OSError -> IOError
This presumes that IOError become OSError in 3.3 as well as 3.4 (#18151). But there are a few existig OSErrors is 3.3 (and that pre-existed the change in 3.4). So there would would need to be a check that a changed line matched an existing 2.7 line.

Harder (2to3 parser?):
print(arglist) -> print arglist  # but what if keyword args?
Outputting "fix print on line nn" would be easiest.

README needed (python -m) test -> (python -m) test.regrtest in the test instructions, but this should be the only place that occurs.

I might put 'edit_patch' or whatever in idle_test.
History
Date User Action Args
2013-06-06 18:29:51terry.reedysetrecipients: + terry.reedy, ned.deily, roger.serwy, asvetlov, Todd.Rovito
2013-06-06 18:29:51terry.reedysetmessageid: <1370543391.75.0.919797325796.issue18152@psf.upfronthosting.co.za>
2013-06-06 18:29:51terry.reedylinkissue18152 messages
2013-06-06 18:29:51terry.reedycreate