- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message202821
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 | vstinner |
|---|---|
| Recipients | christian.heimes, docs@python, pitrou, vstinner |
| Date | 2013-11-14.08:28:01 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1384417682.25.0.829972568274.issue19576@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> Perhaps we can fix PyGILState to call PyEval_InitThreads automatically? Yes, I had the same idea. Here is a patch to call PyEval_InitThreads() in PyGILState_Ensure() for new threads. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-11-14 08:28:02 | vstinner | set | recipients: + vstinner, pitrou, christian.heimes, docs@python |
| 2013-11-14 08:28:02 | vstinner | set | messageid: <1384417682.25.0.829972568274.issue19576@psf.upfronthosting.co.za> |
| 2013-11-14 08:28:02 | vstinner | link | issue19576 messages |
| 2013-11-14 08:28:02 | vstinner | create | |

