[issue7980] time.strptime not thread safe

Brett Cannon added the comment: As per Paul's suggestion, closing as "won't fix" as this only pertains to Python 2.7 and it will not be changing. -- resolution: -> wont fix stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue7980] time.strptime not thread safe

Paul Ganssle added the comment: >From what I can tell, this is a Python 2.7-only bug, and it's not a security >issue, so I think we can close the issue as either "wontfix" (because we won't >fix it in Python 2) or "fixed" (because it is already fixed in Python 3), >depending on your perspect

[issue7980] time.strptime not thread safe

Changes by Martin Panter : -- Removed message: http://bugs.python.org/msg263977 ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue7980] time.strptime not thread safe

Eryk Sun added the comment: SilentGhost, msg263977 is spam copied from msg206393 to try to fool people into clicking on the link. I've marked all of these messages from editor-buzzfeed as spam. -- nosy: +eryksun ___ Python tracker

[issue7980] time.strptime not thread safe

SilentGhost added the comment: Lisa, please be careful with nosy list. -- nosy: +Romuald, SilentGhost, William.McBrine, amaury.forgeotdarc, belopolsky, brett.cannon, ccorbacho, ced, cptnwillard, davidfraser, dpalms2011, epu, eric.smith, flox, fredwheeler, kzsolt, mark.dickinson, matrix

[issue7980] time.strptime not thread safe

lissacoffey added the comment: On the other hand, the way imports are handled in 3.3 and later is a bit different, and if I run the unit test (which does still fail for me on 2.7 tip) on 3.3 and 3.4 tip it passes. Thanks Lisa - python expert mysite: http://www.followthesteps.net/sky-contact-ph

[issue7980] time.strptime not thread safe

Fred Wheeler added the comment: This issue should be noted in the documentation of strptime in the time and datetime modules and/or the thread module. As it stands there is no good way for a user of these modules to learn of this problem until one day the right race conditions exist to expose

[issue7980] time.strptime not thread safe

Antoine Pitrou added the comment: There are probably reasons why the import is currently done lazily, so I would advise against changing this in 2.7, unless the reasons are investigated and clearly understood. -- ___ Python tracker

[issue7980] time.strptime not thread safe

Changes by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue7980] time.strptime not thread safe

Changes by Erik Purins : -- nosy: +epu ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/m

[issue7980] time.strptime not thread safe

Romuald Brunet added the comment: This is a patch attempt to fix issue: import the _strptime module at time / datetime module load instead of method call. Please note that the test is not fully reliable: it may pass without the patch / on current version, since threaded execution isn't control

[issue7980] time.strptime not thread safe

Stéphane Wirtel added the comment: This bug has not been fixed in 2.7.6 on OSX 10.9.2. -- nosy: +matrixise ___ Python tracker ___ ___ P

[issue7980] time.strptime not thread safe

Changes by Romuald Brunet : -- nosy: +Romuald ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue7980] time.strptime not thread safe

R. David Murray added the comment: There's no patch posted here, and the issue is still open, so no. On the other hand, the way imports are handled in 3.3 and later is a bit different, and if I run the unit test (which does still fail for me on 2.7 tip) on 3.3 and 3.4 tip it passes. Given tha

[issue7980] time.strptime not thread safe

David Palms added the comment: I am still seeing this in 2.7.5, has a patch been created yet? -- nosy: +dpalms2011 ___ Python tracker ___ _

[issue7980] time.strptime not thread safe

William McBrine added the comment: I'm still seeing this, in the 2.7.2 that comes with OS X 10.8.2. -- nosy: +William.McBrine ___ Python tracker ___ __

[issue7980] time.strptime not thread safe

Antoine Pitrou added the comment: For the record, issue9260 proposes to fix the issues with PyImport_ImportModuleNoBlock. -- nosy: +pitrou ___ Python tracker ___ ___

[issue7980] time.strptime not thread safe

Changes by Cédric Krier : -- nosy: +ced ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/m

[issue7980] time.strptime not thread safe

Changes by Florent Xicluna : -- nosy: +flox ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue7980] time.strptime not thread safe

Zsolt Kendi added the comment: I recognize the same problem problem at linux with 4 core 64 processor. The python version is 2.6.5 . Looks like occured randomly but maybe this is depend from thread sequence. -- nosy: +kzsolt ___ Python tracker

[issue7980] time.strptime not thread safe

Carlos Corbacho added the comment: As per my comments on Issue11108 - I suspect that PyImport_ImportModuleNoBlock is a bit of a red herring here - in Python 2.5 and earlier versions (well before PyImport_ImportModuleNoBlock was added), we have occasionally seen 'AttributeError: strptime' from

[issue7980] time.strptime not thread safe

Alexander Belopolsky added the comment: It seems to me that this is related to if not a duplicate of issue 8098. -- keywords: -patch ___ Python tracker ___ _

[issue7980] time.strptime not thread safe

MunSic JEONG added the comment: > Do you have a patch to fix the issue? no, I don't. I just wanted to move stage from "unittest needed" to "needs patch" :) After reading issue8098, now I realized that this is broad issue as belopolsky said in msg110095. For new reader of this issue after m

[issue7980] time.strptime not thread safe

Alexander Belopolsky added the comment: RDM> FYI there's been a proposal to create a time.py module anyway RDM> in order to add some pure python functions not worth writing in c. RDM> For reference, it's issue 7989. Issue #7989 was retargeted to deal with datetime module. The time.py issue is

[issue7980] time.strptime not thread safe

Alexander Belopolsky added the comment: MunSic, It looks like issue7980.patch is just a unit test. Do you have a patch to fix the issue? -- ___ Python tracker ___

[issue7980] time.strptime not thread safe

Changes by Antoine Pitrou : -- nosy: +belopolsky stage: unit test needed -> needs patch ___ Python tracker ___ ___ Python-bugs-list mai

[issue7980] time.strptime not thread safe

MunSic JEONG added the comment: Attribute error confirmed on OSX, and py3k. http://codereview.appspot.com/2371041 -- keywords: +patch Added file: http://bugs.python.org/file19133/issue7980.patch ___ Python tracker

[issue7980] time.strptime not thread safe

Changes by MunSic JEONG : -- nosy: +ruseel ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue7980] time.strptime not thread safe

Changes by David Fraser : -- nosy: +davidfraser ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue7980] time.strptime not thread safe

R. David Murray added the comment: Attribute error confirmed on linux on trunk and py3k. -- priority: -> normal stage: -> test needed ___ Python tracker ___ ___

[issue7980] time.strptime not thread safe

Eric Smith added the comment: I just tried it again under gdb on MacOS 10.6, the supplied python 2.6.4 and got this backtrace: Program received signal SIGTRAP, Trace/breakpoint trap. [Switching to process 61133] 0x7fff87a4b790 in __CFInitialize () (gdb) bt #0 0x7fff87a4b790 in __CFIni

[issue7980] time.strptime not thread safe

R. David Murray added the comment: FYI there's been a proposal to create a time.py module anyway in order to add some pure python functions not worth writing in c. -- nosy: +r.david.murray ___ Python tracker _

[issue7980] time.strptime not thread safe

Brett Cannon added the comment: Lib/_strptime.py itself should be thread-safe. I am guessing that it has something to do with the way the C code in time.c imports _strptime.py. A possible solution if it is the C code's import stuff is to create a time.py that imports a _time.c, but that's a t

[issue7980] time.strptime not thread safe

Eric Smith added the comment: Oops, sorry for not specifying that. It's: Python 2.6.4 (r264:75706, Jan 27 2010, 12:09:19) [GCC 4.2.1 (Apple Inc. build 5646) (dot 1)] on darwin -- ___ Python tracker ___

[issue7980] time.strptime not thread safe

Eric Smith added the comment: With 10.6's stock python, I've had this test either work or crash Python. On trunk, I get it to either work or give the same error as the original report. Unfortunately I've been unable to get it to crash again in a debugger so I can get a stack trace. But I'm st

[issue7980] time.strptime not thread safe

New submission from Willard : The following script raises several "_strptime_time" AttributeErrors (on OS X 10.4 at least). If time.strptime is used before starting the threads, then no exception is raised (the issue may thus come from strptime.py not being imported in a thread safe manner).