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 EdSchouten
Recipients EdSchouten, akira, belopolsky, lemburg, pitrou, tim.peters, vstinner
Date 2016-09-14.19:21:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
As a person who keeps a close eye on the Austin Group mailing lists (i.e., 'the POSIX working group'), my guess is that it's very unlikely that POSIX will ever add those *_s() extensions. Here's a discussion on Reddit that actually captures all of the arguments pretty well:

That said, any API will do. The localtime_r() function has the disadvantage that the return value is a bit odd: can it return any other tm structure than the one provided? localtime_s() is a bit weird in that its input argument is stored after the output argument. Both functions also unnecessarily pass the time_t by reference. Maybe we can just pick a prototype that's as Pythonesque as possible that also fixes these shortcomings. Any thoughts?
Date User Action Args
2016-09-14 19:21:42EdSchoutensetrecipients: + EdSchouten, lemburg, tim.peters, belopolsky, pitrou, vstinner, akira
2016-09-14 19:21:42EdSchoutensetmessageid: <>
2016-09-14 19:21:42EdSchoutenlinkissue28148 messages
2016-09-14 19:21:42EdSchoutencreate