On Wed, Jan 16, 2013 at 11:59 AM, <v...@googlecode.com> 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 available on this platform. > > > Nope. It is available anywhere, but pythoninterp=dynamic is the only choice > if you want to have both python and python3 support in one binary. It is > Gentoo on amd64. And Ubuntu ARM (efika MX smartbook modification of Ubuntu, > stripped of almost any package that was there in a fresh installation). > >> Reverting commit 7f10daa706bb solves the issue (the test-case is correclty >> incrementing the variable in background). It also prevents vim to compile >> when PY_CAN_RECURSE is not set. > > > Now when you mentioned it I remember I saw some (threading?) problems with > this commit on vim-dev. Did not came to my mind as I forgot about threads as > they are not working on ARM and are not forcefully terminatable. This is > also why I suggest processes to anyone wanting to use threads. > > Though reverting commit is not an option: it itself is solving some issues. > Better to check why I have the code running correctly and you do not.
Perhaps this problem is related with the one that I've reported two moths ago: https://groups.google.com/forum/?fromgroups=#!topic/vim_dev/1B2habthlBs -- Jakson Alves de Aquino Federal University of Ceará Social Sciences Department www.lepem.ufc.br/aquino.php -- 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
