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 thorsten.behrens
Recipients brian.curtin, eric.araujo, loewis, mhammond, skrah, tarek, thorsten.behrens
Date 2010-12-24.22:28:36
SpamBayes Score 1.76882e-11
Marked as misclassified No
Message-id <>
Thank you for that patch, Stefan. I am currently tinkering with bringing pycrypto to 3.x and ran into this issue. initfunc2.patch resolves the issue on Win7-64, python31-64.

I don't feel comfortable releasing code that requires the user to manually patch Python to build. What are my options here? Go back to void instead of PyMODINIT_FUNC? Is there aught else I can do to make sure pycrypto will build well "in the wild"?
Date User Action Args
2010-12-24 22:28:43thorsten.behrenssetrecipients: + thorsten.behrens, loewis, mhammond, tarek, eric.araujo, brian.curtin, skrah
2010-12-24 22:28:43thorsten.behrenssetmessageid: <>
2010-12-24 22:28:36thorsten.behrenslinkissue9709 messages
2010-12-24 22:28:36thorsten.behrenscreate