[Python-Dev] Fixing the GIL (with a BFS scheduler) (original) (raw)
Terry Reedy tjreedy at udel.edu
Mon May 17 21:39:36 CEST 2010
- Previous message: [Python-Dev] Fixing the GIL (with a BFS scheduler)
- Next message: [Python-Dev] Fixing the GIL (with a BFS scheduler)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 5/17/2010 2:59 PM, Bill Janssen wrote:
Yes, it would. As soon as I have working 3.x versions of BeautifulSoup, PIL, ReportLab, JCC, pylucene, pyglet, nltk, email, epydoc, feedparser, dictclient, docutils, hachoir, mutagen, medusa, python-dateutil, and vobject, I'll let you know. :-)
There /has/ been momentum in fixing it. In py3k. Yes, I specifically meant in the 2.x branch. I'm guessing I'll have to stay on 2.x for at least 5 more years, due to the other package dependencies.
I suspect it will be sooner than that, especially if users like you ask/beg/plead with the maintainers of libraries like those you listed to make them work with 3.2. Give your particular reason, that Python3 will work increasingly well with multicore machines. I an sure a couple of such people have posted that they see no reason to upgrade until users start requesting them to.
Terry Jan Reedy
- Previous message: [Python-Dev] Fixing the GIL (with a BFS scheduler)
- Next message: [Python-Dev] Fixing the GIL (with a BFS scheduler)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]