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 false on is_alive().. Here is an example of the issue. You can see i've imported uuid. This script should fork into the background and stay alive for at least 3 loops (3 seconds) but it dies after 1 loop as self._thread.is_alive() return False?? http://paste.pound-python.org/show/WbDkqPqu94zEstHG6Xl1/ This does NOT happen in py 2.7 or py3.3. Only occurs py3.4+ ---------- components: Interpreter Core messages: 263640 nosy: Steven Adams priority: normal severity: normal status: open title: uuid causing thread issues when forking using os.fork py3.4+ versions: Python 3.4, Python 3.5 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26793> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
