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 jeffr@livedata.com
Recipients amaury.forgeotdarc, benjamin.peterson, georg.brandl, jeffr@livedata.com, pitrou, python-dev, skrah
Date 2012-03-22.20:29:21
SpamBayes Score 0.003391224
Marked as misclassified No
Message-id <1332448162.51.0.120796128346.issue14387@psf.upfronthosting.co.za>
In-reply-to
Content
Stefan asked

'Did you include Python.h before or after Windows.h? Extensions
are supposed to include Python.h before anything else. '

I downloaded http://code.google.com/p/apsw/ to test it out on the latest sqlite release.  I followed the build instructions on its website and discovered this problem.  

While the code isn't mine, inspecting apsw.c, the main source file, I can see that the sqlite "amalgamation" is included BEFORE Python.h.  It is this "amalgamation" that, in turn, includes Windows.h.

Should I contact the extension's author(s)/maintainer(s) and tell them about this ordering requirement?
History
Date User Action Args
2012-03-22 20:29:22jeffr@livedata.comsetrecipients: + jeffr@livedata.com, georg.brandl, amaury.forgeotdarc, pitrou, benjamin.peterson, skrah, python-dev
2012-03-22 20:29:22jeffr@livedata.comsetmessageid: <1332448162.51.0.120796128346.issue14387@psf.upfronthosting.co.za>
2012-03-22 20:29:21jeffr@livedata.comlinkissue14387 messages
2012-03-22 20:29:21jeffr@livedata.comcreate