[issue31990] Pickling deadlocks in thread with python -m

2020-12-03 Thread Werner Smidt
Werner Smidt added the comment: Thanks for going to the trouble, Sara. Curiosity remains, but I'll mark this as closed. -- stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/i

[issue31990] Pickling deadlocks in thread with python -m

2020-12-01 Thread Werner Smidt
Werner Smidt added the comment: Sorry for being lacking in providing some OS info. b Opensuse Tumbleweed, Linux kernel 5.8.10-1, Intel system I cannot explain why, but relating to Sara's answer, if you remove the .join() statements at the end, you get the following exception: /usr/bin

[issue31990] Pickling deadlocks in thread with python -m

2020-11-30 Thread Werner Smidt
Werner Smidt added the comment: The condition still stands. if I execute: python3 testqueuepickle3.py Everything is fine. If, however I execute: python3 -m testqueuepickle3.py It hangs. -- versions: +Python 3.8 ___ Python tracker <ht

[issue31990] Pickling deadlocks in thread with python -m

2020-11-30 Thread Werner Smidt
Change by Werner Smidt : -- status: pending -> open Removed file: https://bugs.python.org/file47255/testqueuepickle.py ___ Python tracker <https://bugs.python.org/issu

[issue31990] Pickling deadlocks in thread with python -m

2017-11-09 Thread Werner Smidt
New submission from Werner Smidt <werner.sm...@gmail.com>: Hi there I recently stumbled on an interesting behaviour. I won't call it an error, because I think it's a mistake I made. BACKGROUND: I want to spawn threads that handle pickled data. This works really well. However, I