Opened 3 years ago

#12679 new defect

flashproxy programs don't allow intermixed positional and optional arguments

Reported by: dcf Owned by: dcf
Priority: Low Milestone:
Component: Archived/Flashproxy Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Since #9975 (merge of argparse), it's an error if you put an optional argument between positional arguments.

works:        flashproxy-client --external :0 :0
works:        flashproxy-client :0 :0 --external
doesn't work: flashproxy-client :0 --external :0

The error you get is:

$ ./flashproxy-client :0 --external :0 
usage: flashproxy-client --register [OPTIONS] [LOCAL][:PORT] [REMOTE][:PORT]
flashproxy-client: error: unrecognized arguments: :0

How it used to look is:

$ ./flashproxy-client :0 --external :0 
2014-07-22 09:10:54 Listening remote on 0.0.0.0:43803.
2014-07-22 09:10:54 Listening remote on [::]:45211.
2014-07-22 09:10:54 Listening local on 127.0.0.1:60759.
2014-07-22 09:10:54 Listening local on [::1]:33344.

I'm calling it minor because probably most people don't try to do this.

The analogous ticket for fog is #10004.

Child Tickets

Change History (0)

Note: See TracTickets for help on using tickets.