Hi all,
For the time being, I'm handling the snow leopard builds of MacVim
from my github account[1]. Björn got a report[2] of that build having
problems with python path issues and asked me to look in to it. I'm
away from my Snow Leopard computer for a few days so I'm hoping
someone else on the list can try to confirm this for me. Anyone? I'm
just looking for the python path info from within MacVim:
python << ENDPYTHON
import sys
print sys.path
ENDPYTHON
On Wednesday, May 16, 2012 at 4:10 PM, Alex Lovell-Troy wrote:
> Hi all,
> For the time being, I'm handling the snow leopard builds of MacVim
> from my github account[1]. Björn got a report[2] of that build having
> problems with python path issues and asked me to look in to it. I'm
> away from my Snow Leopard computer for a few days so I'm hoping
> someone else on the list can try to confirm this for me. Anyone? I'm
> just looking for the python path info from within MacVim:
> python << ENDPYTHON
> import sys
> print sys.path
> ENDPYTHON
> --
> You received this message from the "vim_mac" 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
Alex: I am guessing that you have Homebrew or something similar
installed and the build picked up the wrong Python version. I think
one easy workaround is to add the switch "--with-macsdk=10.6" when you
build (if memory serves me correctly). If not, message me personally
and we'll sort it out.
I might release a new snapshot in the coming days, so I don't think it
necessary to build a new version just yet (unless you want to, of
course).
On Thu, May 17, 2012 at 4:17 AM, björn <bjorn.winck...@gmail.com> wrote:
> On Wed, May 16, 2012 at 9:13 PM, Cássio Marques <cassio...@gmail.com> wrote:
> Alex: I am guessing that you have Homebrew or something similar
> installed and the build picked up the wrong Python version. I think
> one easy workaround is to add the switch "--with-macsdk=10.6" when you
> build (if memory serves me correctly). If not, message me personally
> and we'll sort it out.
> I might release a new snapshot in the coming days, so I don't think it
> necessary to build a new version just yet (unless you want to, of
> course).
> Björn
> --
> You received this message from the "vim_mac" 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
It's been a couple of weeks and I haven't heard of a new snapshot
being ready, but to make sure I can still build on this old laptop, I
fixed the bug and uploaded a new build to github.
For those of you not interested in using the built-in python
interpreter, there's no reason to switch. Of course, I'm sure there
are at least a few of you for which this will make life slightly
easier.
On Thu, May 17, 2012 at 11:32 AM, Alex Lovell-Troy <farmk...@gmail.com> wrote:
> Aye. Looks like my goof here. I'll get a new snapshot build this
> weekend if at all possible and definitely when björn releases his.
> -alex
> On Thu, May 17, 2012 at 4:17 AM, björn <bjorn.winck...@gmail.com> wrote:
>> On Wed, May 16, 2012 at 9:13 PM, Cássio Marques <cassio...@gmail.com> wrote:
>> Alex: I am guessing that you have Homebrew or something similar
>> installed and the build picked up the wrong Python version. I think
>> one easy workaround is to add the switch "--with-macsdk=10.6" when you
>> build (if memory serves me correctly). If not, message me personally
>> and we'll sort it out.
>> I might release a new snapshot in the coming days, so I don't think it
>> necessary to build a new version just yet (unless you want to, of
>> course).
>> Björn
>> --
>> You received this message from the "vim_mac" 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
