Michael Chermside mcherm at mcherm.com
Tue Aug 17 19:19:37 CEST 2004

• Previous message: [Python-Dev] Python 3.0 list of goals
• Next message: [Python-Dev] Find out whether PyEval_InitThreads has been called?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

> Why not go one step further and make all locking
> operations in python no-ops if PyEval_InitThreads has never been
> called?  Currently, we risk python crashing if we call such functions
> without calling PyEval_InitThreads.

+1. Seems like it can't possibly hurt, and as you say, it's trivial
to implement.

-- Michael Chermside

---

• Previous message: [Python-Dev] Python 3.0 list of goals
• Next message: [Python-Dev] Find out whether PyEval_InitThreads has been called?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list