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 | Rhamphoryncus |
|---|---|
| Recipients | Rhamphoryncus, benjamin.peterson, christian.heimes, gregory.p.smith, roudkerk, schmir |
| Date | 2008年06月11日.23:57:49 |
| SpamBayes Score | 0.04410798 |
| Marked as misclassified | No |
| Message-id | <1213228672.29.0.441457880161.issue1683@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Incidentally, it doesn't seem necessary to reinitialize the lock. Posix duplicates the lock, so if you hold it when you fork your child will be able to unlock it and use it as normal. Maybe there's some non-Posix behaviour or something even more obscure when #401226 was done? (reinitializing is essentially harmless though, so in no way should this hold up release.) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年06月11日 23:57:52 | Rhamphoryncus | set | spambayes_score: 0.044108 -> 0.04410798 recipients: + Rhamphoryncus, gregory.p.smith, christian.heimes, schmir, roudkerk, benjamin.peterson |
| 2008年06月11日 23:57:52 | Rhamphoryncus | set | spambayes_score: 0.044108 -> 0.044108 messageid: <1213228672.29.0.441457880161.issue1683@psf.upfronthosting.co.za> |
| 2008年06月11日 23:57:51 | Rhamphoryncus | link | issue1683 messages |
| 2008年06月11日 23:57:49 | Rhamphoryncus | create | |