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 terry.reedy
Recipients bethard, docs@python, eric.araujo, jaraco, terry.reedy
Date 2011-12-14.05:25:26
SpamBayes Score 5.3198864e-06
Marked as misclassified No
Message-id <1323840327.81.0.105431690915.issue13540@psf.upfronthosting.co.za>
In-reply-to
Content
My guess from the way the docs are written now is that subclassing from Action and over-riding just the __call__ method is the intended way, not just the recommended. If so, Action is a quasi-private class, only exposed so it could be subclassed with one method given. And if so, one could question whether anything more need be documented.

However, in your patch, you write

"+Many actions also override the ``__init__`` method, validating the parameters to the argument definition and raising a ValueError or other Exception on failure."

What 'many actions' are you referring to? Ones you have written, by referring to the code? Ones you think might be written if the doc were added?

In any case, I would prefer input from Stephen before we expose and thereby freeze the __init__ signature.
History
Date User Action Args
2011-12-14 05:25:27terry.reedysetrecipients: + terry.reedy, jaraco, bethard, eric.araujo, docs@python
2011-12-14 05:25:27terry.reedysetmessageid: <1323840327.81.0.105431690915.issue13540@psf.upfronthosting.co.za>
2011-12-14 05:25:27terry.reedylinkissue13540 messages
2011-12-14 05:25:26terry.reedycreate