Message225756
| Author |
jaraco |
| Recipients |
BreamoreBoy, bethard, docs@python, eric.araujo, jaraco, paul.j3, python-dev, terry.reedy, tshepang |
| Date |
2014年08月23日.18:41:55 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1408819315.94.0.472307097316.issue13540@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I have no idea why that would be. I used the same syntax for the Action class as ArgumentParser. From the latest tip:
.. class:: ArgumentParser(prog=None, usage=None, description=None, \
epilog=None, parents=[], \
...
.. class:: Action(option_strings, dest, nargs=None, const=None, default=None,
type=None, choices=None, required=False, help=None,
metavar=None)
I don't know what would cause those to render differently. Perhaps you're suggesting a difference elsewhere. In any case, I don't see any action I can take to address your concern. |
|