Martin v. Löwis wrote: > People running into these problems will have a number of choices to > them: switch operating systems (i.e. drop OSX for something that > actually works), switch programming languages (i.e. drop Python for > something that actually works), switch application architectures (i.e. > drop threads for something that actually works), switch to 3.x, or > just accept the problem, and hope that the system will find something > else to do while switching Python threads.
There's even another option: if the new-GIL backport patch in http://bugs.python.org/issue7753 works for you, apply it and run with it (and advocate for a Python 2.8 release to make it more widely available, possibly even contributing the fallback behaviour discussed in the issue to make that situation more likely). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --------------------------------------------------------------- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
