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 barry, brett.cannon, gvanrossum, larry, meador.inge, ncoghlan, skrah, tim.peters, yselivanov, zach.ware
Date 2014-01-24.13:54:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390571653.84.0.838637196905.issue20189@psf.upfronthosting.co.za>
In-reply-to
Content
Okay, I'm checking this beast in.  Hooray!  Thanks for your reviews, everybody!

--

I thought it was still possible to introduce objects into Python at runtime without calling PyType_Ready on their type.  If that's true,
then there wouldn't necessarily *be* a type creation time at which
we could do the signature splitting.

Is that no longer allowed as of 3.4?  Are all types required to be
registered with PyType_Ready before objects of that type are introduced into the Python runtime?  If so, hooplah!
History
Date User Action Args
2014-01-24 13:54:13larrysetrecipients: + larry, gvanrossum, tim.peters, barry, brett.cannon, ncoghlan, skrah, meador.inge, zach.ware, yselivanov
2014-01-24 13:54:13larrysetmessageid: <1390571653.84.0.838637196905.issue20189@psf.upfronthosting.co.za>
2014-01-24 13:54:13larrylinkissue20189 messages
2014-01-24 13:54:13larrycreate