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 rhettinger
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-26.23:41:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I believe that the behavior is so deeply ingrained in how argparse
> works that it can't be changed.

I think so as well.  Handling arguments with a dash prefiew could be viewed as fundamental design flaw except for the fact that the module has been so successful (both before and after landing in the standard library).

I've come to believe that argparse is very difficult to change without risk of breaking many existing tools that depend on argparse working exactly the way it does now.

Also, this issue is over a decade old and no clear solution has emerged.

> 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.

I agree. It would be a hard sell at this point.

Let's close this one.  I don't think it is going to get solved.
Date User Action Args
2021-12-26 23:41:14rhettingersetrecipients: + rhettinger, cben, amcnabb, bethard, eric.smith, 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-26 23:41:14rhettingersetmessageid: <>
2021-12-26 23:41:14rhettingerlinkissue9334 messages
2021-12-26 23:41:14rhettingercreate