On Jun 19, 2013 7:54 PM, "Bram Moolenaar" <[email protected]> wrote: > > > ZyX wrote: > > > > > On Jun 19, 2013 12:10 AM, "Bram Moolenaar" <[email protected]> wrote: > > > > > > > > > > > > > > > Test 86 passes without problems when using a dynamically loaded Python. > > > > > When using a static library I get the different output below. > > > > > > > > > > This is on Ubuntu 12.10 with Python 2.7.3. > > > > > > > > > > Test 87 has the same problem: OK with dynamic loading, fails with static > > > > > library. See further down below. Python 3.2.3. > > > > > > > > Unable to reproduce with neither debugging semi-static (it still does use > > > > ld-linux.so to link) python-2.3, -2.6 and -2.7 builds or with non-debuging > > > > semi-static python-2.7, though with the latter different error pops out > > > > which needs to be solved. There are also a few compiler warnings in case of > > > > semi-static build. > > > > > > Keep in mind that building with both python2 and python3 may > > > automatically switch do dynamic libraries. At least that happens on my > > > system. > > > > Is not it the only option to build with both because of conflicting symbol > > names? Before testing I excluded python 3. And did not get *this* failure > > as I reported, though found some other one which is not in your report. > > I hope we can make the tests depend less on the specific Python version > and environment. I understand it's not easy. But ignoring test > failures because "that one always fails" will hide real problems.
I do not argue that we should do this. But I can't fix things that work for me because I have no idea what is broken. Note that in your report + prefixes right lines though so I should focus not on deducing the reason of the difference, but find out why it shows NotImplementedError in my case (refer to the discussion of this issue happened previously). Likely this will fix the difference as well. > > By the way, is not it better to fail in place of switching to dynamic > > builds? I always compiled both versions with explicit =dynamic flags each > > time I wanted both pythons because I know it being the only option, but if > > I did not know this and requested semi-static ones and did get dynamic > > instead I would be surprised. The only case I would care about it is static > > build (fully static!) I once needed, but here I would be surprised very > > badly if I did not find python support due to such autoswitching. > > It's been like this for a long time. In practice it appears to work. > > Of course it's not at all nice that :py3 does not work after :py, but > there is no good alternative. > > -- > hundred-and-one symptoms of being an internet addict: > 252. You vote for foreign officials. > > /// 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.
