[Python-Dev] The endless GIL debate: why not remove thread support instead? (original) (raw)
Michael Foord fuzzyman at voidspace.org.uk
Sat Dec 13 14:32:36 CET 2008
- Previous message: [Python-Dev] The endless GIL debate: why not remove thread support instead?
- Next message: [Python-Dev] The endless GIL debate: why not remove thread support instead?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Lennart Regebro wrote:
On Fri, Dec 12, 2008 at 02:13, Sturla Molden <sturla at molden.no> wrote:
I genuinely think the use of threads should be discouraged. It leads to code that are full of bugs and difficult to maintain - race conditions, deadlocks, and livelocks are common pitfalls.
The use of threads for load balancing should be discouraged, yes. That is not what they are designed for. Threads are designed to allow blocking processes to go on in the background without blocking the main process. This, they are very useful for. Removing thread support would therefore be a very big mistake. It's needed, it has it's uses, just not the one you want.
That's an interesting assertion about what threads were designed for. Do you have anything to back it up?
Michael
-- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog
- Previous message: [Python-Dev] The endless GIL debate: why not remove thread support instead?
- Next message: [Python-Dev] The endless GIL debate: why not remove thread support instead?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]