This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.smith
Recipients Christophe.Guillon, Clint Olsen, Socob, abacabadabacaba, amcnabb, andersk, bethard, cben, danielsh, davidben, drm, eric.araujo, eric.smith, evaned, fennec15, gaborjbernat, gdb, gfxmonk, karzes, maggyero, martin.panter, memeplex, nelhage, orivej, paul.j3, porton, r.david.murray, rhettinger, skilletaudio, spaceone, xtreak
Date 2021-12-24.05:41:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
@karzes: If you read all of the messages above, you'll find that the behavior is deeply baked in to argparse. So, no, there is no fix for this issue.

I'm not sure about others, but I believe that the behavior is so deeply ingrained in how argparse works that it can't be changed. I have the same desire as you: to use a command line parser that works like all other Unix commands. I've switched my personal code to click. There's also Appeal, typer, and others.

Unlike when argparse was added to the stdlib, at this point installing modules from PyPI is sufficiently easy that I'm not sure it makes sense to advocate for another command line parser in the stdlib.
Date User Action Args
2021-12-24 05:41:59eric.smithsetrecipients: + eric.smith, rhettinger, cben, amcnabb, bethard, orivej, eric.araujo, r.david.murray, memeplex, gfxmonk, evaned, andersk, abacabadabacaba, gdb, nelhage, drm, davidben, martin.panter, paul.j3, skilletaudio, Christophe.Guillon, danielsh, spaceone, Clint Olsen, porton, Socob, maggyero, karzes, xtreak, fennec15, gaborjbernat
2021-12-24 05:41:59eric.smithsetmessageid: <>
2021-12-24 05:41:59eric.smithlinkissue9334 messages
2021-12-24 05:41:59eric.smithcreate