Updates:
Status: Fixed
Comment #15 on issue 103 by brammool...@gmail.com: Python thread are not
running in background
http://code.google.com/p/vim/issues/detail?id=103
The patch is included as 7.3.786.
Please reopen this issue if it didn't fix the problem.
--
--
You received this mes
Comment #14 on issue 103 by degu...@gmail.com: Python thread are not
running in background
http://code.google.com/p/vim/issues/detail?id=103
That patch seems to fix the issue indeed.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text
Comment #13 on issue 103 by jonathan...@gmail.com: Python thread are not
running in background
http://code.google.com/p/vim/issues/detail?id=103
Here is how I patched my source.
Attachments:
vim-python-thread-issue.patch 974 bytes
--
--
You received this message from the "vim_dev"
Updates:
Status: Accepted
Comment #12 on issue 103 by lech.lor...@gmail.com: Python thread are not
running in background
http://code.google.com/p/vim/issues/detail?id=103
I also noticed the problem when using clang_complete. Last time closing Vim
took 2 hours to complete! I'm using
Comment #11 on issue 103 by degu...@gmail.com: Python thread are not
running in background
http://code.google.com/p/vim/issues/detail?id=103
Changing the initial value of pygilstate to PyGILState_LOCKED may be the
solution? (I'm only supposing since I don't know how the initial bug could
Comment #10 on issue 103 by degu...@gmail.com: Python thread are not
running in background
http://code.google.com/p/vim/issues/detail?id=103
Hum, I'm wondering whether the GIL is not taken too much time.
If we read the description of PyEval_InitThreads(), it says "it is
guaranteed that the
Comment #9 on issue 103 by degu...@gmail.com: Python thread are not running
in background
http://code.google.com/p/vim/issues/detail?id=103
Maybe the bug depend on python's version? Mine is 2.7.3.
And yes I know that reverting the culprit commit is not really an option:
it does fix a bug.
Replies from mailing list are not added to bug tracker:
http://code.google.com/p/vim/issues/detail?id=103. Use commenting there.
--
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.v
On Wed, Jan 16, 2013 at 11:59 AM, wrote:
> Comment #8 on issue 103 by zyx@gmail.com: Python thread are not running
> in background
> http://code.google.com/p/vim/issues/detail?id=103
>
>> On which platform are you testing? I would guess Windows since
>> pythoninterp=dynamic seems to only be a
Comment #8 on issue 103 by zyx@gmail.com: Python thread are not running
in background
http://code.google.com/p/vim/issues/detail?id=103
On which platform are you testing? I would guess Windows since
pythoninterp=dynamic seems to only be available on this platform.
Nope. It is availabl
Comment #7 on issue 103 by degu...@gmail.com: Python thread are not running
in background
http://code.google.com/p/vim/issues/detail?id=103
I did find the culprit!
Reverting commit 7f10daa706bb solves the issue (the test-case is correclty
incrementing the variable in background). It also p
Comment #6 on issue 103 by degu...@gmail.com: Python thread are not running
in background
http://code.google.com/p/vim/issues/detail?id=103
I just tried manually disabling PY_CAN_RECURSE from if_python.c, and the
thread seems to be running in background. In clang_complete the correct
beha
Comment #5 on issue 103 by degu...@gmail.com: Python thread are not running
in background
http://code.google.com/p/vim/issues/detail?id=103
Yes you're right about multithreading. I'm just afraid of the cost of
sending completion results from the "completion process".
But anyway, this is n
Comment #4 on issue 103 by zyx@gmail.com: Python thread are not running
in background
http://code.google.com/p/vim/issues/detail?id=103
I also use Python2 for the test, but I use both pythoninterp=dynamic and
python3interp=dynamic on amd64 and AFAIR non-dynamic python2-only builds on
Comment #3 on issue 103 by degu...@gmail.com: Python thread are not running
in background
http://code.google.com/p/vim/issues/detail?id=103
Spawning process instead of thread is not an option in my case…
I just tried with a vim-7.3.762 and can still reproduce 100% of the time. I
should hav
Comment #2 on issue 103 by zyx@gmail.com: Python thread are not running
in background
http://code.google.com/p/vim/issues/detail?id=103
Similar to the one you linked in
http://marc.info/?l=vim&m=110029576819749&w=2. And it in fact runs fine
here (vim-7.3.762, amd64).
--
You received
Comment #1 on issue 103 by zyx@gmail.com: Python thread are not running
in background
http://code.google.com/p/vim/issues/detail?id=103
Wondering whether it depends on the kind of code that is executed in the
thread. I did successfully launch threads that are only sleeping and then
in
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 103 by degu...@gmail.com: Python thread are not running in
background
http://code.google.com/p/vim/issues/detail?id=103
Hi,
While trying to fix an issue on clang_complete plugin
(https://github.com/Rip-Rip/clang_complete
18 matches
Mail list logo
