Christian wrote:
>
> Joe Holloway schrieb:
> > ImportError: Failed to import _strptime because the import lockis
> > [sic] held by another thread.
>
> The error message is my fault. The cause of the mistake is obvious:
No worries. The error message is clear even with the minor typo, I
just wanted
Joe Holloway schrieb:
> We recently uplifted our web application to run on Python 2.6.2.
> We've noticed on a couple occasions that calls into time.strptime have
> failed with this exception:
>
> ImportError: Failed to import _strptime because the import lockis
> [sic] held by another thread.
The
MRAB wrote:
Joe Holloway wrote:
We recently uplifted our web application to run on Python 2.6.2.
We've noticed on a couple occasions that calls into time.strptime have
failed with this exception:
[2] http://svn.python.org/view?view=rev&revision=59678
A simple workaround might be to sleep a sho
Joe Holloway wrote:
We recently uplifted our web application to run on Python 2.6.2.
We've noticed on a couple occasions that calls into time.strptime have
failed with this exception:
ImportError: Failed to import _strptime because the import lockis
[sic] held by another thread.
I poked around
We recently uplifted our web application to run on Python 2.6.2.
We've noticed on a couple occasions that calls into time.strptime have
failed with this exception:
ImportError: Failed to import _strptime because the import lockis
[sic] held by another thread.
I poked around the source code enough
