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 belopolsky
Recipients EdSchouten, akira, belopolsky, lemburg, pitrou, tim.peters, vstinner
Date 2016-09-14.18:56:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473879394.01.0.636516281639.issue28148@psf.upfronthosting.co.za>
In-reply-to
Content
> we should likely introduce full wrappers that have a name starting with _PyTime_, right?


Yes, and I would like to give some thought to what the best API would be. The two choices are to emulate localtime_r on Windows or emulate localtime_s on POSIX. While localtime_r is probably a better known function, localtime_s has been standardized by C11 and may appear on POSIX platforms in the future.

Also, I think _PyTime_localtime_r/s should include the 

 #ifdef EINVAL
         if (errno == 0)
             errno = EINVAL;
 #endif

code that is repeated everywhere in the current codebase.
History
Date User Action Args
2016-09-14 18:56:34belopolskysetrecipients: + belopolsky, lemburg, tim.peters, pitrou, vstinner, akira, EdSchouten
2016-09-14 18:56:34belopolskysetmessageid: <1473879394.01.0.636516281639.issue28148@psf.upfronthosting.co.za>
2016-09-14 18:56:33belopolskylinkissue28148 messages
2016-09-14 18:56:33belopolskycreate