[issue6362] multiprocessing: handling of errno after signals in sem_acquire()

2014-06-22 Thread Martin v . Löwis
Martin v. Löwis added the comment: Thanks, closing as fixed. -- nosy: +loewis resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue6362] multiprocessing: handling of errno after signals in sem_acquire()

2014-06-22 Thread Tumer Topcu
Tumer Topcu added the comment: Nevermind the last comment (curse of using a loaner laptop), tried again after compiling against the latest repo all works as expected. I believe this issue can be closed. -- ___ Python tracker

[issue6362] multiprocessing: handling of errno after signals in sem_acquire()

2014-06-22 Thread Tumer Topcu
Tumer Topcu added the comment: Looks like the suggested fix is there in v2.7.6: do { Py_BEGIN_ALLOW_THREADS if (blocking && timeout_obj == Py_None) res = sem_wait(self->handle); else if (!blocking) res = sem_trywait(self->handle); else

[issue6362] multiprocessing: handling of errno after signals in sem_acquire()

2010-08-27 Thread Mark Lawrence
Changes by Mark Lawrence : -- stage: -> needs patch versions: -Python 2.6, Python 3.0 ___ Python tracker ___ ___ Python-bugs-list mai

[issue6362] multiprocessing: handling of errno after signals in sem_acquire()

2010-08-27 Thread Ask Solem
Changes by Ask Solem : -- nosy: +asksol ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/m

[issue6362] multiprocessing: handling of errno after signals in sem_acquire()

2009-06-28 Thread Jesse Noller
Jesse Noller added the comment: Thank you Ryan -- assignee: -> jnoller priority: -> normal ___ Python tracker ___ ___ Python-bugs-li

[issue6362] multiprocessing: handling of errno after signals in sem_acquire()

2009-06-28 Thread Ryan Leslie
Changes by Ryan Leslie : -- nosy: +jnoller ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue6362] multiprocessing: handling of errno after signals in sem_acquire()

2009-06-28 Thread Ryan Leslie
New submission from Ryan Leslie : While developing an application, an inconsistency was noted where, depending on the particular signal handler in use, multiprocessing.Queue.put() may (or may not) raise OSError() after sys.exit() was called by the handler. The following example, which was tested