[issue35442] Chain of several subcommands in argparse

[paul j3]

Change by paul j3 :


--
nosy: +paul.j3

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35442] Chain of several subcommands in argparse

[Terry J. Reedy]

Terry J. Reedy  added the comment:

A better place to discuss format and API is python-ideas list.  Almost 
certainly will see responses there.

--
nosy: +terry.reedy
stage:  -> test needed
versions: +Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35442] Chain of several subcommands in argparse

[Victor Porton]

Victor Porton  added the comment:

One of possible solutions:
https://bugs.python.org/issue35480

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35442] Chain of several subcommands in argparse

[Victor Porton]

New submission from Victor Porton :

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.

--
components: Library (Lib)
messages: 331393
nosy: porton
priority: normal
severity: normal
status: open
title: Chain of several subcommands in argparse
type: enhancement

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com