#41344: vim @7.4.052_0+breakindent+huge+python27+python33 - vim breaks with two Python versions ---------------------+---------------------- Reporter: ml@… | Owner: raimue@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: vim | ---------------------+---------------------- Changes (by raimue@…): * status: new => assigned Comment: Please be aware that only one version of python can be loaded at a time in vim anyway. This is the correct way this is supposed to work and documented in `:help python-2-and-3`. But the problems you encountered are probably really broken behavior. I could reproduce the issue with `:python3 import sys` and it's clearly missing the path to the frameworks directory here. I am looking into this. However, I could not reproduce the second issue with `:python import sys` and `MAXREPEAT` on Mavericks. It could be you are seeing an upstream issue introduced in 2.7.4 (http://bugs.python.org/issue18050). Was your vim built against python27 @2.7.4 and then python27 was upgraded later on? -- Ticket URL: <https://trac.macports.org/ticket/41344#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X

#41344: vim @7.4.052_0+breakindent+huge+python27+python33 - vim breaks with two Python versions ---------------------+---------------------- Reporter: ml@… | Owner: raimue@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: vim | ---------------------+---------------------- Comment (by raimue@…): Oh well, it's an old problem returning. Turns out that both `DYNAMIC_PYTHON3_DLL` and `DYNAMIC_PYTHON_DLL` are set to relative paths to the framework. That makes vim pick up the Python 2.7 from /System/Library/Frameworks -- which works on Mavericks, as it is 2.7.5, but fails on Mountain Lion and earlier as it is an incompatible <= 2.7.3. Of course, it fails for Python 3.3, as that does not exist in OS X itself. I am pretty sure this is broken since r108762 (#39223), which changed the `LINKFORSHARED` variable and removed the part that previously added an absolute path to the framework. I am working on a patch. -- Ticket URL: <https://trac.macports.org/ticket/41344#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X

#41344: vim @7.4.052_0+breakindent+huge+python27+python33 - vim breaks with two Python versions ---------------------+---------------------- Reporter: ml@… | Owner: raimue@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: vim | ---------------------+---------------------- Comment (by code@…): I am currently on Mac OS 10.9.2 and Xcode 5.1 (Build version 5B130a according to `xcodebuild -version`). For the sake of clarity: {{{ $ port echo requested py27-pip @1.5.4_0 py27-virtualenvwrapper @4.0_0 py33-pip @1.5.4_0 py33-virtualenvwrapper @4.0_0 python27 @2.7.6_0 python33 @3.3.5_0 vim @7.4.052_0+breakindent+cscope+huge+python27+python33 }}} It was not immediately apparent to me how to apply the patch. For the benefit of others: {{{ $ sudo port uninstall vim $ cd /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/editors/vim/files $ sudo curl -O https://trac.macports.org/raw-attachment/ticket/41344/vim- python-linkage.diff $ sudo patch < vim-python-linkage.diff $ sudo rm vim-python-linkage.diff $ sudo port install -s vim +breakindent +cscope +huge +python27 +python33 }}} I started without a `.vimrc` or `.vim/` bundle directory. Starting `vim` and entering the following results in a segfault. {{{ :py print "Hello" :py3 print("Bonjour") }}} Specifically, the terminal prints: {{{ Vim: Caught deadly signal SEGV Vim: Finished. Segmentation fault: 11 }}} However, the following runs absolutely fine: {{{ :py3 print("Bonjour") :py print "Hello" :py3 print("Konichiwa") }}} What's more, after running the commands above, I am able to see the following: {{{ :python print sys.prefix /opt/local/Library/Frameworks/Python.framework/Versions/2.7 :python3 print(sys.prefix) /opt/local/Library/Frameworks/Python.framework/Versions/3.3 }}} I rebuilt my `.vimrc` file, checking the commands and bundles as I went. None of the native settings or commands I use in `vim` caused any problems. The only (`vundle`) package that caused problems was `Lokaltog/powerline`, which caused any command to `:py3` to segfault as above. The rest of my bundles (below) work fine. * gmarik/vundle * scrooloose/nerdtree * ervandew/supertab * tpope/vim-fugitive * scrooloose/syntastic * davidhalter/jedi-vim * vim-scripts/django.vim Notably, `jedi-vim` caused no issue, but I was unable to test whether it was using omnicompletion for Python version 2 or 3. I would love help here: is there a command that will tell me which Python version is loaded? `has()` will attempt to dynamically load Python, and is not useful in this context. The behaviors described above are erratic and undesirable. I'm increasingly under the impression that this is not a MacPorts problem, and much more a `vim` problem. Is the version of `vim` being used in MacPorts the Unix version, or one of the Mac OS X flavors? Essentially: who should I go to with this bug? -- Ticket URL: <https://trac.macports.org/ticket/41344#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X

#41344: vim @7.4.052_0+breakindent+huge+python27+python33 - vim breaks with two Python versions ---------------------+---------------------- Reporter: ml@… | Owner: raimue@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: vim | ---------------------+---------------------- Comment (by code@…): Apologies for the confusion: I was simply confirming the behavior you'd mentioned, expanding on some of the details, and seeking a direction to take this in. I will try to see whether I can recreate the problem with the current version of vim for Unix, and then contact the vim_dev list depending on my results. I'll let you know if I find anything interesting. -- Ticket URL: <https://trac.macports.org/ticket/41344#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X