[Python-3000] threading, part 2 (original) (raw)
Aahz aahz at pythoncraft.com
Sat Aug 12 15:44:28 CEST 2006
- Previous message: [Python-3000] Python 2.5 release schedule (was: threading, part 2)
- Next message: [Python-3000] Draft pre-PEP: function annotations
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Aug 11, 2006, Luis P Caamano wrote:
That's how I feel too Josiah. In some ways, it's the same as writing device drivers in a pre-emptable kernel. You can get interrupted and pre-empted by the hardware at any freaking time in any piece of code and your memory might go away so you better pin it and deal with the interrupts. Forget about that and you end up with a nice kernel panic. Still, we have all kinds of device drivers on SMP, pre-emptable kernels. It can be done.
But Python is not the language/platform to do it.
(Yeah, someone else said that already, but I think it needs emphasis.)
Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." --Brian W. Kernighan
- Previous message: [Python-3000] Python 2.5 release schedule (was: threading, part 2)
- Next message: [Python-3000] Draft pre-PEP: function annotations
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]