Message 69393 - 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	rogerbinns
Recipients	amaury.forgeotdarc, loewis, rogerbinns
Date	2008-07-07.19:18:50
SpamBayes Score	2.65559e-05
Marked as misclassified	No
Message-id	<1215458332.12.0.835517367326.issue3308@psf.upfronthosting.co.za>
In-reply-to

Content
In MinGW's defense the MSVC 7 dll does include localtime. Since Python/distutils only says that MSVC 9 dll is being used at link time, how exactly is MinGW (or any other code) supposed to know that localtime should be provided some other way? Maybe distutils should be defining __MSVCRT_VERSION__ to 0x0900 for the compile phase as well for Python 2.6/3.0. If that was the case then at least I could work around the issue (the localtime call isn't actually in my code but a library I statically link in) and still work correctly on earlier Pythons which don't need any workarounds.

In MinGW's defense the MSVC 7 dll does include localtime.  Since
Python/distutils only says that MSVC 9 dll is being used at link time,
how exactly is MinGW (or any other code) supposed to know that localtime
should be provided some other way?  Maybe distutils should be defining 
__MSVCRT_VERSION__ to 0x0900 for the compile phase as well for Python
2.6/3.0.  If that was the case then at least I could work around the
issue (the localtime call isn't actually in my code but a library I
statically link in) and still work correctly on earlier Pythons which
don't need any workarounds.

History
Date	User	Action	Args
2008-07-07 19:18:52	rogerbinns	set	spambayes_score: 2.65559e-05 -> 2.65559e-05 recipients: + rogerbinns, loewis, amaury.forgeotdarc
2008-07-07 19:18:52	rogerbinns	set	spambayes_score: 2.65559e-05 -> 2.65559e-05 messageid: <1215458332.12.0.835517367326.issue3308@psf.upfronthosting.co.za>
2008-07-07 19:18:51	rogerbinns	link	issue3308 messages
2008-07-07 19:18:50	rogerbinns	create