. > > > Not surprising. Also, I forgot about the GIL, which truely limits the > > performance benifits of threading in Python. If anything ever kills > > Python, I bet it'll be the GIL (but I'm hopeful that it'll get removed > > before it causes an untimely death...) > > Maybe you can remove it :-) > > William
Of course, this is the penultimate reason that going multi-threaded in python is insane... not only do you get the opportunity to learn all about synchronization and thread management, you also enjoy non- deterministic bugs which only take days or weeks to solve whereas more conventional logic bugs take many many minutes, sometimes even hours. (From a Keynesian economics perspective, going multi-threaded is justified just by the added work) Best of all: you don't get any performance benefit from threading!!!. Imagine: we can get intermittent complex code which can't be easily debugged (high cost) with no benefit. My guess is the government would fund this work based on the cost-benefit analysis alone. -glenn --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
