Ken Takata wrote:
> 2013/01/31 Thu 5:56:41 UTC+9 Bram Moolenaar wrote:
>
> > That doesn't look right, it would access pygilstate before setting it.
>
> Hmm, but the same can be said of if_python.c. pygilstate would be
> accessed in Python_SaveThread() because PY_CAN_RECURSE is normally defined.
>
> Using PyEval_SaveThread() to release the GIL seems good.
> I checked the attached patch with Python 2.7 and 3.3 on Win7.
> Both background threads and system trace seem to work well.
The implementaiton for Python 2 was supposed to work.
I would appreciate a few people to try this out on different
environments. If I don't hear about problems I'll include this patch.
--
ARTHUR: Listen, old crone! Unless you tell us where we can buy a shrubbery,
my friend and I will ... we will say "Ni!"
CRONE: Do your worst!
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
