Steven Adams added the comment:
anyone got any other thoughts on this??
--
___
Python tracker
<http://bugs.python.org/issue26793>
___
___
Python-bugs-list mailin
Steven Adams added the comment:
Ok but the question still remains, why does it only happen on py3.4+??
--
___
Python tracker
<http://bugs.python.org/issue26
Steven Adams added the comment:
My workaround didn't work either.. We are a number of third party libs
including flask. As soon as i import flask the issues remains.. Maybe something
with flask is importing ctypes?
Something aint
Steven Adams added the comment:
Shouldn't that mean it also breaks on py3.3?
As a workaround i just import uuid later within the thread method.
--
___
Python tracker
<http://bugs.python.org/is
Steven Adams added the comment:
I forgot to mention if i remove import uuid all works as expected.
--
___
Python tracker
<http://bugs.python.org/issue26
New submission from Steven Adams:
I've ran into a strange issue after trying to port a project to support py 3.x
The app uses a double os.fork to run in the background. On py 3.4+ it seems
that when you have an import uuid statement it causes threading.threads to
always return fal
