This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rcohen
Recipients brian.curtin, jnoller, kevinwatters, lemburg, nascheme, pitrou, rcohen, schmir
Date 2010-01-27.00:16:44
SpamBayes Score 3.1713937e-10
Marked as misclassified No
Message-id <20100126161336.0b5af0a6@neeble>
In-reply-to <1264270988.68.0.841510050993.issue7753@psf.upfronthosting.co.za>
Content
On Sat, 23 Jan 2010 18:23:10 +0000
Antoine Pitrou <report@bugs.python.org> 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.

Ross
History
Date User Action Args
2010-01-27 00:16:47rcohensetrecipients: + rcohen, lemburg, nascheme, pitrou, schmir, kevinwatters, jnoller, brian.curtin
2010-01-27 00:16:45rcohenlinkissue7753 messages
2010-01-27 00:16:44rcohencreate