R. David Murray added the comment: Well, we want it to apply to python3 as well, since we want to see jython support python3 eventually :)
Also, optparse is present in python3 for backward compatibility reasons only...there were very few changes between the time python3 branched from python2 and argparse superceeded optparse. So the differences between the two code bases should be minimal. Obviously you can't test against jython3, since it doesn't exist, but what you can do is make the patch based on the python2 optparse, and then see if the patch applies cleanly to python3. It probably won't, but as far as I can see from a quick diff, most of the changes will be related to the changes between python2 syntax and python3 syntax, and will be easy to forward port even without being able to test it directly against jython. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1704474> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
