Ken Takata wrote: > Bram Moolenaar wrote: > > > Patch 7.3.786 > > Problem: Python threads don't run in the background (issue 103). > > Solution: Move the statements to manipulate thread state. > > Files: src/if_python.c > > There is the same problem with if_python3. > Following patch seems to fix this (but I'm not sure): > > --- a/src/if_python3.c > +++ b/src/if_python3.c > @@ -734,6 +734,8 @@ > * as the system trace hook), will be lost between invocations of > * Python code. */ > PyEval_InitThreads(); > + /* The first python thread is vim's, release the lock. */ > + PyGILState_Release(pygilstate); > pygilstate = PyGILState_Ensure(); > > #ifdef DYNAMIC_PYTHON3
That doesn't look right, it would access pygilstate before setting it. -- If your life is a hard drive, Christ can be your backup. /// 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.
