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 larry, serhiy.storchaka
Date 2014-01-19.04:39:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390106403.12.0.602072346214.issue20294@psf.upfronthosting.co.za>
In-reply-to
Content
Here's a patch.  Wasn't as easy as I thought, it kind of took all day.

Changes include:

* __init__ and __new__ always take kwargs.
  * if the function signature doesn't accept keyword arguments,
    it calls _PyArg_NoKeywords().
* __init__ returns int, not PyObject *.
* __init__ and __new__ should support all argument parsing
  scenarios (unpack tuple, positional only, etc).

Pre-exiting behavior:
* The C function basename chosen for __new__ is just the name of
  the class, it doesn't end in __new__.
* The methoddef #define is suppressed.
History
Date User Action Args
2014-01-19 04:40:03larrysetrecipients: + larry, serhiy.storchaka
2014-01-19 04:40:03larrysetmessageid: <1390106403.12.0.602072346214.issue20294@psf.upfronthosting.co.za>
2014-01-19 04:40:03larrylinkissue20294 messages
2014-01-19 04:39:59larrycreate