Marc-Andre Lemburg <m...@egenix.com> added the comment: Ross Cohen wrote: >> By the way, the new GIL only works with POSIX and Windows NT threading APIs. >> Perhaps it can't be backported at all to 2.x, given that 2.x supports more >> threading APIs than py3k does? > > Looking at the Python/thread_*.h files, it looks like py3k still > supports 9 different threading models. If that's accurate, it means > py3k trunk is broken on platforms which use cthread, lwp, os2, pth, > sgi, solaris and wince threading models. The 2.x series adds atheos and > beos to that list. > > I think the right way to fix this is to extend the thread_*.h files to > have a proper abstraction for conditions which can be used by the > newgil work. Then the maintainers for more obscure platforms can fix > those instead of it all turning into a big mess in ceval_gil.h.
I find it rather strange that Python 3.x now only supports NT and POSIX threads in ceval while it still supports the whole set of other thread implementations for the _thread module. Has this been discussed on python-dev ? Why can't the code necessary to get the new GIL working be added to Sjoerd's portable thread library ? As it stands, I think this is a bummer for both Python 2.7 and 3.2. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7753> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
