- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message307571
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 | gvanrossum |
|---|---|
| Recipients | Mekk, eric.snow, gvanrossum, ncoghlan, pitrou, steve.dower, vstinner, xcombelle |
| Date | 2017-12-04.15:38:00 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <CAP7+vJ+1-28T2O2_64qCbdaBr1n0OKw+zMf0r1-RO+exniZCrg@mail.gmail.com> |
| In-reply-to | <1512389671.82.0.213398074469.issue20891@psf.upfronthosting.co.za> |
| Content | |
|---|---|
Yeah, the original reasoning was that threads were something esoteric and not used by most code, and at the time we definitely felt that always using the GIL would cause a (tiny) slowdown and increase the risk of crashes due to bugs in the GIL code. I'd be happy to learn that we no longer need to worry about this and can just always initialize it. (Note: I haven't read the entire thread, just the first and last message.) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-12-04 15:38:00 | gvanrossum | set | recipients: + gvanrossum, ncoghlan, pitrou, vstinner, Mekk, eric.snow, steve.dower, xcombelle |
| 2017-12-04 15:38:00 | gvanrossum | link | issue20891 messages |
| 2017-12-04 15:38:00 | gvanrossum | create | |

