Ken Takata wrote:
> 2013/02/02 Sat 4:23:57 UTC+9 Bram Moolenaar wrote:
>
> > 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.
>
> No one has repo
Hi,
2013/02/02 Sat 4:23:57 UTC+9 Bram Moolenaar wrote:
> 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.
No one has reported about my patch :-(
BTW, I
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
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
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
Hi,
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
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
*** ../vim-7.3.785/src/if_python.c 2012-10-21 01:46:56.0 +0200
--- src/if_python.c 2013-01-30
