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 larry
Recipients Arfrever, Jim.Jewett, Trundle, alex, asvetlov, barry, bfroehle, chris.jerdonek, daniel.urban, david.villa, dmalcolm, eric.smith, ezio.melotti, gregory.p.smith, gvanrossum, jcea, jkloth, larry, mark.dickinson, ncoghlan, pitrou, scoder, serhiy.storchaka, skrah, v+python
Date 2013-02-25.23:37:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1361835473.36.0.0024006225683.issue16612@psf.upfronthosting.co.za>
In-reply-to
Content
A quick note about the extension mechanism.  Currently the only way to extend PyArg_Parse* is via O&.  Therefore, any extended type you add will use O&, and will have a "converter".  So internally all I did was say "if the parameter has a converter, ignore the type and use the O& format unit".

This may not be the perfect extension API, if we change Clinic to using some new yet-to-be-defined API for argument parsing.  But I suspect it's pretty close.  Extension types will need a conversion function from PyObject to their type, they'll need a way of defining the C default value, and they'll need a way of cleaning up afterwards, all of which I already do.  So I guess I'm interested in feedback on the extension API too.
History
Date User Action Args
2013-02-25 23:37:53larrysetrecipients: + larry, gvanrossum, barry, gregory.p.smith, jcea, mark.dickinson, ncoghlan, pitrou, scoder, eric.smith, jkloth, ezio.melotti, Arfrever, v+python, alex, Trundle, asvetlov, skrah, dmalcolm, daniel.urban, chris.jerdonek, Jim.Jewett, serhiy.storchaka, bfroehle, david.villa
2013-02-25 23:37:53larrysetmessageid: <1361835473.36.0.0024006225683.issue16612@psf.upfronthosting.co.za>
2013-02-25 23:37:53larrylinkissue16612 messages
2013-02-25 23:37:53larrycreate