This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | Pankrat |
|---|---|
| Recipients | Pankrat, benjamin.peterson, jyasskin |
| Date | 2008年03月20日.01:32:48 |
| SpamBayes Score | 0.42884114 |
| Marked as misclassified | No |
| Message-id | <1205976772.37.0.221961465006.issue2320@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Hi, I narrowed the problem down to the creation of the error pipe in _execute_child: >> errpipe_read, errpipe_write = os.pipe() >> self._set_cloexec_flag(errpipe_write) If I protect these two lines with a lock, I cannot reproduce the hang anymore (tested against Python 2.5.1). I'm not yet sure why this should be atomic (as there are no classic race condition problems involved AFAICT). By the way, this is on Linux: > uname -a Linux jade 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月20日 01:32:52 | Pankrat | set | spambayes_score: 0.428841 -> 0.42884114 recipients: + Pankrat, jyasskin, benjamin.peterson |
| 2008年03月20日 01:32:52 | Pankrat | set | spambayes_score: 0.428841 -> 0.428841 messageid: <1205976772.37.0.221961465006.issue2320@psf.upfronthosting.co.za> |
| 2008年03月20日 01:32:51 | Pankrat | link | issue2320 messages |
| 2008年03月20日 01:32:50 | Pankrat | create | |