You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Committed in r76276 through r76281, along with removing 'g' from the
getopt list in 2.6. 3.1 still has other traces of the -g option; I
haven't cleaned that up.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: