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 | christian.heimes |
|---|---|
| Recipients | andyshorts, christian.heimes, ocean-city |
| Date | 2008年01月19日.13:52:22 |
| SpamBayes Score | 0.0071382616 |
| Marked as misclassified | No |
| Message-id | <1200750743.77.0.914049516755.issue1720705@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
For 2.6 I've fixed several places where C code was importing a Python module in a non-threadsafe way. In general a thread start must never be caused by an import and only the main thread should import modules. Imports within or caused-by a thread other than the main thread isn't safe. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年01月19日 13:52:24 | christian.heimes | set | spambayes_score: 0.00713826 -> 0.0071382616 recipients: + christian.heimes, ocean-city, andyshorts |
| 2008年01月19日 13:52:23 | christian.heimes | set | spambayes_score: 0.00713826 -> 0.00713826 messageid: <1200750743.77.0.914049516755.issue1720705@psf.upfronthosting.co.za> |
| 2008年01月19日 13:52:22 | christian.heimes | link | issue1720705 messages |
| 2008年01月19日 13:52:22 | christian.heimes | create | |