classification
Title: Chain of several subcommands in argparse
Type: enhancement Stage: test needed
Components: Library (Lib) Versions: Python 3.8
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: paul.j3, porton, terry.reedy
Priority: normal Keywords:

Created on 2018-12-08 21:58 by porton, last changed 2018-12-26 22:36 by paul.j3.

Messages (3)
msg331393 - (view) Author: Victor Porton (porton) Date: 2018-12-08 21:58
We should consider some way to implement argparse functionality asked here:

https://stackoverflow.com/q/53686523/856090

It is unclear how exactly to do this. This message is a call to discuss what should be the information format and API.

The awful thing is that I may need to write my own command line parser, as current argparse seems to be unable to provide this functionality.

I think, I will implement this for my program sooner or later but the idea to write my own analogue of argparse somehow terrifies me.
msg331731 - (view) Author: Victor Porton (porton) Date: 2018-12-13 01:46
One of possible solutions:
https://bugs.python.org/issue35480
msg331857 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2018-12-14 19:29
A better place to discuss format and API is python-ideas list.  Almost certainly will see responses there.
History
Date User Action Args
2018-12-26 22:36:40paul.j3setnosy: + paul.j3
2018-12-14 19:29:04terry.reedysetversions: + Python 3.8
nosy: + terry.reedy

messages: + msg331857

stage: test needed
2018-12-13 01:46:21portonsetmessages: + msg331731
2018-12-08 21:58:49portoncreate