Message315711
Paul. This is a bug, not a feature in argparse. Devin is 100% correct. According to the docs REMAINDER should be greedy and is used for passing arguments to sub commands. In your example the expected behavior is that if you do put "d --foo x a b c" that --foo is none and args gets everything. We shouldn't need to use a gatekeeper or resort to manually parsing the remainder arguments. It also shouldn't take 5 years to acknowledged that it needs to be fixed. I'm happy to make a patch if its a bandwidth issue. Am I misunderstanding and you feel like its not possible to fix? I guess if there is a backward compatibility issue then we need to write a new option that does literally return the remainder arguments as documented. |
|
Date |
User |
Action |
Args |
2018-04-24 18:13:31 | aldencolerain | set | recipients:
+ aldencolerain, bethard, chris.jerdonek, paul.j3, danielsh |
2018-04-24 18:13:31 | aldencolerain | set | messageid: <1524593611.55.0.682650639539.issue17050@psf.upfronthosting.co.za> |
2018-04-24 18:13:31 | aldencolerain | link | issue17050 messages |
2018-04-24 18:13:31 | aldencolerain | create | |
|