Message 179498 - Python tracker

➜

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	ncoghlan
Recipients	Arfrever, Gregory.Andersen, amaury.forgeotdarc, franck, georg.brandl, lemburg, ncoghlan, pitrou, serhiy.storchaka, skrah, stutzbach, vstinner
Date	2013-01-09.23:10:51
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<CADiSq7dPfKtXDvMTOTJhV5=zLmqOR=UOVtqz4HD6P+NToXgunA@mail.gmail.com>
In-reply-to	<1357772053.04.0.661587544729.issue10156@psf.upfronthosting.co.za>

Content
There should still be a check in tp_new (IIRC) that calls PyType_Ready on unready types. While doing something systematic about this kind of problem is part of the rationale of PEP 432, that won't help earlier versions.

There should still be a check in tp_new (IIRC) that calls PyType_Ready on
unready types.

While doing something systematic about this kind of problem is part of the
rationale of PEP 432, that won't help earlier versions.

History
Date	User	Action	Args
2013-01-09 23:10:52	ncoghlan	set	recipients: + ncoghlan, lemburg, georg.brandl, amaury.forgeotdarc, pitrou, vstinner, stutzbach, Arfrever, skrah, serhiy.storchaka, franck, Gregory.Andersen
2013-01-09 23:10:52	ncoghlan	link	issue10156 messages
2013-01-09 23:10:51	ncoghlan	create