Re: convert-ly broken on Mac OS X "Tiger"?

[Graham Percival]

That's not the issue.  The issue is that convert-ly calls
  /usr/bin/python
which is 2.3.5 for you (and me).

Cheers,
- Graham

On Fri, 12 Sep 2008 15:55:38 -0700
"David Fedoruk" <address@hidden> wrote:

> Hello:
> 
> I recall that one of the pages in the Lilypond documentation
> specifically for Mac OS X suggested a second way to set environmental
> variables via Property LIst. I created that suggested Property List
> but the path for Python began /System/Library (I cut and pasted it
> from the example.
> 
> However typing env in a command line window reveals this path for
> python:
> 
> PATH=/Library/Frameworks/Python.framework/Versions/Current/bin
> 
> No System in front of it!
> 
> I installed the Mac OS X Python package as well, so there was a
> conflict between those two paths. I logged out of my account and
> logged back in to see if the change had been made. convert-ly still
> failed. I've restarted and attempted convert-ly with the same results.
> 
> My current version of python:
> 
> Python -V
> Python 2.5.2
> 
> Python shell:
> 
> Python 2.5.2 (r252:60911, Feb 22 2008, 07:57:53)
> [GCC 4.0.1 (Apple Computer, Inc. build 5363)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
> >>>
> 
> which Python:
> 
> /Library/Frameworks/Python.framework/Versions/Current/bin/Python
> 
> env
> 
> PYTHON_DATADIR=/Library/Frameworks/Python.framework/Versions/Current/bin/
> PATH=/Library/Frameworks/Python.framework/Versions/Current/bin: (etc.)
> 
> Mac OS X 10.4.11 PPC 1Ghz iBook G4
> 
> The only change I can see to make would be to be more explicit in the
> Property List and add the line as in the result of "which".
> 
> David
> 
> 
> 
> On Fri, Sep 12, 2008 at 11:33 AM, Graham Percival <address@hidden>
> wrote:
> > On Fri, 12 Sep 2008 06:14:30 -0700
> > Kurt Kroon <address@hidden> wrote:
> >
> >> I just upgraded my Python installation to version 2.5.2 (via
> >> MacPython), but I'm still getting that error.
> >>
> >> (I even renamed my dev install, just in case Mac OS X didn't like
> >> the space I used to have in the name.)
> >>
> >> So is this a problem with the MacPython package?
> >> Is it time for me to dig into my system's (and Python's) guts?
> >
> > That would be a complete waste of time.  See my message on Sep 2
> > to this list.  Search for "env python".
> >
> > Cheers,
> > - Graham
> >
> >
> > _______________________________________________
> > lilypond-user mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/lilypond-user
> >
> 
> 
> 
> -- 
> David Fedoruk
> 
> http://recordjackethistorian.wordpress.com
> "Music is enough for one's life time, but one life time is not enough
> for music" Sergei Rachmaninov
> 
> 
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-user