Message95249
In forward porting a patch to py3k I noticed that there is a 'g' option
in the optparse argument list in regrtest in 2.x that is not present in
3.x. But the surprising thing was that there are no docs for this
option, nor any option handler in the 2.x regrtest.
I propose to add an 'else' case to the option parsing loop that asks the
user to report a bug if it is handed an unknown option. Patch attached.
My one question is whether this might have been intentional for backward
compatibility reasons: let -g be passed and ignore it silently. I'm
guessing it was just a deletion oversight, though. |
|
Date |
User |
Action |
Args |
2009-11-14 18:43:11 | r.david.murray | set | recipients:
+ r.david.murray, pitrou |
2009-11-14 18:43:11 | r.david.murray | set | messageid: <1258224191.28.0.763058552728.issue7324@psf.upfronthosting.co.za> |
2009-11-14 18:43:09 | r.david.murray | link | issue7324 messages |
2009-11-14 18:43:09 | r.david.murray | create | |
|