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 georg.brandl, larry
Date 2014-01-11.23:32:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1389483179.45.0.391886551562.issue20186@psf.upfronthosting.co.za>
In-reply-to
Content
1)
Wow.  I never knew about PyArg_UnpackTuple.  You're right, those should be converted too.  Hooray, more entry points to convert.

I'll write something up for the howto about UnpackTuple.

I just did a quick check, and there are 96 entry points (by my count) that use PyArg_UnpackTuple().  Shall I create Derby issues #19 and #20, or do you have a better idea?

2) For FUNC1 / 1A / 2 macros: right now you'd have to just copy and paste over and over.  There might be something you could do with a [python] block where you automatedly reuse the existing sigantures.  I was thinking about having Clinic support it directly, maybe with the syntax:

/*[clinic input]
func_name = existing_func_name

docstring goes here
[...]*/

You'd skip the parameters and the return annotation.  You could only reuse functions from the current file.  Would that be a big boon to you?
History
Date User Action Args
2014-01-11 23:32:59larrysetrecipients: + larry, georg.brandl
2014-01-11 23:32:59larrysetmessageid: <1389483179.45.0.391886551562.issue20186@psf.upfronthosting.co.za>
2014-01-11 23:32:59larrylinkissue20186 messages
2014-01-11 23:32:58larrycreate