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 mhammond
Recipients mhammond
Date 2014-04-26.08:00:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398499255.25.0.881446688113.issue21354@psf.upfronthosting.co.za>
In-reply-to
Content
Python 3.3 and earlier have in methodobject.c:

/* PyCFunction_New() is now just a macro that calls PyCFunction_NewEx(),
   but it's part of the API so we need to keep a function around that
   existing C extensions can call.
*/

#undef PyCFunction_New
PyAPI_FUNC(PyObject *) PyCFunction_New(PyMethodDef *, PyObject *);

which means PyCFunction_New is exported from the DLL.  Python 3.4 does not have this (which seems a bug in its own right given the comment in 3.3 and earlier) but PC/bdist_wininst/install.c has code that attempts to dynamically load this function from the DLL and fails, causing 3rd party installers to fail.

Assuming the removal of this API was intentional so the problem is that install.c needs to be updated, the following patch fixes the issue.
History
Date User Action Args
2014-04-26 08:00:55mhammondsetrecipients: + mhammond
2014-04-26 08:00:55mhammondsetmessageid: <1398499255.25.0.881446688113.issue21354@psf.upfronthosting.co.za>
2014-04-26 08:00:55mhammondlinkissue21354 messages
2014-04-26 08:00:54mhammondcreate