[issue20039] Missing documentation for argparse.ArgumentTypeError

Change by Yassir Karroum : -- keywords: +patch nosy: +ukarroum nosy_count: 6.0 -> 7.0 pull_requests: +29304 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31125 ___ Python tracker

[issue20039] Missing documentation for argparse.ArgumentTypeError

Change by Rahul Kumaresan : -- nosy: +rahul-kumi ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue20039] Missing documentation for argparse.ArgumentTypeError

Nicholas Chammas added the comment: Just a note that I also went looking for the docs for argparse.ArgumentTypeError after coming across it in this (highly viewed) post: https://stackoverflow.com/a/14117511/877069 -- nosy: +nchammas ___ Python

[issue20039] Missing documentation for argparse.ArgumentTypeError

paul j3 added the comment: A related closed request: https://bugs.python.org/issue30220 that wants to test ValueError for non-generic message, instead of using ArgumentTypeError. -- ___ Python tracker

[issue20039] Missing documentation for argparse.ArgumentTypeError

Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +bethard type: - enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20039 ___ ___

[issue20039] Missing documentation for argparse.ArgumentTypeError

New submission from Arnaut Billings: There is no documentation for argparse.ArgumentTypeError: http://docs.python.org/3/library/unittest.html Though it does appear in an example and its usage is simple enough to decipher what it means, it would none the less look more professional if there

[issue20039] Missing documentation for argparse.ArgumentTypeError

paul j3 added the comment: In argparse.py the status of ArgumentTypeError is ambiguous. ArgumentError is listed as a public class, ArgumentTypeError is not. It also says 'All other classes in this module are considered implementation details.' ArgumentTypeError is a subclass of Exception

[issue20039] Missing documentation for argparse.ArgumentTypeError

Arnaut Billings added the comment: It seems what you're saying is that the ArgumentTypeError class should not be public, but being able to raise is should be public. If that's the case, I think it would be more clear to have an argparse.raiseArgumentTypeError method and document when it