Message 165874 - 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	loewis
Recipients	alexandre.vassalotti, asvetlov, daniel.urban, loewis, meador.inge, mstefanro, ncoghlan, rhettinger, yselivanov
Date	2012-07-19.20:23:24
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1342729405.27.0.689088466666.issue15397@psf.upfronthosting.co.za>
In-reply-to

Content
Andrew is right: PyCFunction_NewEx must stay, and must continue to get the same parameters as it currently does. This not only applies to extensions already built, but also to extensions that are built against the new header files: they still need to run under old Python releases (if they only use the stable ABI).

Andrew is right: PyCFunction_NewEx must stay, and must continue to get the same parameters as it currently does. This not only applies to extensions already built, but also to extensions that are built against the new header files: they still need to run under old Python releases (if they only use the stable ABI).

History
Date	User	Action	Args
2012-07-19 20:23:25	loewis	set	recipients: + loewis, rhettinger, ncoghlan, alexandre.vassalotti, asvetlov, meador.inge, daniel.urban, mstefanro, yselivanov
2012-07-19 20:23:25	loewis	set	messageid: <1342729405.27.0.689088466666.issue15397@psf.upfronthosting.co.za>
2012-07-19 20:23:24	loewis	link	issue15397 messages
2012-07-19 20:23:24	loewis	create