| Linking the Python opcodes to Apple Python 2.3 definitely seems like the
right choice on 10.4. The question is what happens with the Python opcodes
on 10.5? Do they get loaded by Csound or is an error message displayed?
Here is how I've revised the text. I'll wait to see if this is correct
before changing the web site again. (I'm considering moving some or all of
this text to the FAQ page as it is getting rather complicated).
Python-compatibility note: All of the latest Mac OS X packages are
built on OS X 10.4 "Tiger" and include a Python opcode module and a
Python interface module that are compatible with the Apple-supplied
Python 2.3 on 10.4. Optionally, if you have installed MacPython 2.4
or 2.5 on 10.4, you can choose the package below that matches your
version of Python (and CPU) to obtain a Python interface module that
will work with your installed Python. The Python opcode module
always uses the Apple-supplied Python 2.3 on 10.4.
While most components in these packages will also work on OS X 10.5,
the Python API interface (csnd module) will not work without
additional configuration and the Python opcodes may not work at all.
Even though OS X 10.5 comes with Python 2.5, the easiest solution
for obtaining a working Python csnd module is to install MacPython
2.5 and then install the Csound package with support for MacPython
2.5. Another solution on 10.5 that will also provide working Python
opcodes is to compile Csound from sources, using whichever version
of Python you have installed.
csound5.09-OSX10.4-Intel.tar.gz
Installer for Intel Macs running OS X 10.4 or higher ("Tiger" or
"Leopard") with MacPython 2.4 or Apple Python (2.3).
csound5.09-OSX10.4-Py2.5-Intel.tar.gz
Installer for Intel Macs running OS X 10.4 or higher ("Tiger" or
"Leopard") with MacPython 2.5 or Apple Python (2.3).
Csound5.09-OSX10.4-PPC.tar.gz
Installer for PowerPC Macs running OS X 10.4 or higher ("Tiger" or
"Leopard") with MacPython 2.4 or Apple Python (2.3).
victor wrote on 9/23/08 2:17 PM:
> Mostly OK, but I would say this for 10.5: the best option is
> to download and install MacPython 2.5 rather than moving files,
> which is untested.
>
> Also: the Py2.5 includes the csnd module for Apple's supplied 2.3.
>
> An added complication: the python opcodes are linked to Apple's
> supplied 2.3, and so their use in combination with
> MacPython 2.4 and 2.5 csnd module is possibly problematic.
>
> Why linking them to 2.3? Well there is a simple answer: if I linked
> them to any other version, I would then require users to install
> MacPython (similar issues to Windows, if any of you follow the
> discussions on the other list). I want to avoid this at all costs.
>
> In OSX10.5, when we have the proper installer, this issue will
> probably disappear.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net |