[issue22697] Deadlock with writing to stderr from forked process

2014-11-02 Thread Serhiy Storchaka

Serhiy Storchaka added the comment:

Sorry. I thought issue6721 is more general, not just about the logging module.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue22697] Deadlock with writing to stderr from forked process

2014-11-02 Thread Charles-François Natali

Charles-François Natali added the comment:

> Maries Ionel Cristian added the comment:
>
> Serhiy, I don't think this is a duplicate. Odd that you closed this without 
> any explanation.
>
> This happens in a internal lock in cpython's runtime, while the other bug is 
> about locks used in the logging module (which are very different).

Yes, this is a duplicate. Whether the lock is an internal or a user-created one 
doesn't change anything, it's always the same problem of having a lock locked 
by another thread at the time of the fork().

--
resolution:  -> duplicate
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue22697] Deadlock with writing to stderr from forked process

2014-11-02 Thread Maries Ionel Cristian

Maries Ionel Cristian added the comment:

Serhiy, I don't think this is a duplicate. Odd that you closed this without any 
explanation.

This happens in a internal lock in cpython's runtime, while the other bug is 
about locks used in the logging module (which are very different).

--
resolution: duplicate -> 
status: closed -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue22697] Deadlock with writing to stderr from forked process

2014-11-02 Thread Serhiy Storchaka

Changes by Serhiy Storchaka :


--
nosy: +serhiy.storchaka
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Locks in the standard library should be sanitized on fork

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue22697] Deadlock with writing to stderr from forked process

2014-11-01 Thread Nir Soffer

Nir Soffer added the comment:

This is a duplicate of http://bugs.python.org/issue6721

--
nosy: +nirs

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue22697] Deadlock with writing to stderr from forked process

2014-10-24 Thread Antoine Pitrou

Changes by Antoine Pitrou :


--
nosy: +neologix

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue22697] Deadlock with writing to stderr from forked process

2014-10-22 Thread Maries Ionel Cristian

New submission from Maries Ionel Cristian:

Example code:

import os
import sys
import threading


def run():
sys.stderr.write("in parent thread\n")

threading.Thread(target=run).start()
pid = os.fork()
if pid:
os.waitpid(pid, 0)
else:
sys.stderr.write("in child\n")


To run:  while python3 deadlock.py; do; done

Note: does not reproduce if ran with `python -u` (unbuffered)

--
components: IO, Interpreter Core
messages: 229825
nosy: ionel.mc
priority: normal
severity: normal
status: open
title: Deadlock with writing to stderr from forked process
versions: Python 3.3, Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com