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 steve.dower
Recipients Ilya.Kulakov, r.david.murray, steve.dower, tnmurphy, vstinner
Date 2015-10-12.15:43:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1444664587.31.0.475609305751.issue24575@psf.upfronthosting.co.za>
In-reply-to
Content
If they are compiled independently, they should have Py_BUILD_CORE set. 

That flag is meant for the headers, which serve dual purposes, not the module itself. *Any* C file that is part of core should expect that option to be set for when it includes its headers.

All that said, it seems that _datetimemodule.c forces Py_BUILD_CORE on to get access to some extra definitions, which presumably means that somebody at some point wanted to compile it into an extension module. I don't see the use case here though - is there something about its public API that is not stable?
History
Date User Action Args
2015-10-12 15:43:07steve.dowersetrecipients: + steve.dower, vstinner, r.david.murray, Ilya.Kulakov, tnmurphy
2015-10-12 15:43:07steve.dowersetmessageid: <1444664587.31.0.475609305751.issue24575@psf.upfronthosting.co.za>
2015-10-12 15:43:07steve.dowerlinkissue24575 messages
2015-10-12 15:43:07steve.dowercreate