| For what it's worth, I'll reiterate.
It is recommended that anyone doing anything serious in python avoids
the apple-shipped version like the plague.
There are multiple reasons for this; check the pythonmc sig for all
the details, (pythonmac-sig@python.org) but they include their
appalling record of maintaining their shipped version. Afterall, it
would be no problem for Apple to keep it up-to-date in the way they do
with other sw, but they don't (care). In addition, they have now
started to include non-standard proprietary API tools (with no access
to sources) with their python which will trap the unwary.
I understand Victor wanting to be inclusive, but IMO, especially given
the amount of work involved in maintenance, it would be better to make
it a requirement for csound that they use the mac-python version.
D.
On 08/08/2009, at 10:36 AM, Chuckk Hubbard wrote:
> That's what he did, but I just checked his email and he also tried
> Csound 5.10 Intel 10.4. He says "it doesn't install the csound module
> for python 2.5, probably because 10.4 only shipped with Python 2.3." I
> can't check right now.
>
> Great news about the 10.5 Intel machine. I'm not in any hurry for
> Python 2.6 myself, having been told it wouldn't be "standard" for some
> time. Seems like it's being picked up pretty quickly by people.
>
> -Chuckk
>
>
> On Fri, Aug 7, 2009 at 10:03 PM, victor
> wrote:
>> That is because he probably installed the PPC version of Csound 5.10
>> for OSX, which is the only 10.5 installer available.
>> To make it work with Intel, he can try installing
>>
>> 1) MacPython 2.5
>> 2) Csound 5.10 for Intel (OSX 10.4).
>>
>> For the next release I should have a 10.5 Intel machine available to
>> create binaries. I will also move to support Python 2.6 (MacPython),
>> as well as the Apple-installed 2.5.
>>
>> Victor.
>>
>> ----- Original Message ----- From: "Chuckk Hubbard"
>>
>> To:
>> Sent: Friday, August 07, 2009 5:48 PM
>> Subject: [Csnd] Re: Re: Re: MacCsound/QuteCsound/Intel/OSX10.5 --
>> what to
>> do?
>>
>>
>> Hi. While you're on the subject, I don't have 10.5 on Intel, so I
>> haven't been able to test, but a user of my program, which links to
>> Csound, told me he gets this:
>>
>> Installing the PPC version yields the error "ImportError:
>> dlopen(/Library/Python/2.5/site-packages/_csnd.so, 2): no suitable
>> image found. Did find:
>> /Library/Python/2.5/site-packages/_csnd.so: mach-o, but wrong
>> architecture
>> "
>>
>> Using the PPC 10.5 version of 5.10. My program is a front end, so
>> there's no QuteCsound involved, so maybe you guys can't help me.
>> Would
>> either of you be willing to test my program?
>> http://rationale.sourceforge.net -version 0.2
>> If so, and it's not immediately clear what to do to test it, I'd
>> appreciate it if you'd drop me a line. I've delayed announcing my
>> program in some forums (for 3 months) because of this.
>>
>> Thanks a lot.
>> -Chuckk
>>
>> On Sun, Aug 2, 2009 at 1:38 AM, Lou Cohen wrote:
>>>
>>> Thanks, David! that's great to know.
>>>
>>> -Lou
>>>
>>>
>>> On 8/1/09 18:33, "DavidW" wrote:
>>>
>>>> Hi Lou,
>>>>
>>>> I run Csound5.09-OSX10.4-PPC
>>>>
>>>> on an Intel Mac under OS 10.5 when I want to use MacCsound
>>>> which I install from a downloaded package.
>>>>
>>>> David
>>>>
>>>> On 02/08/2009, at 1:23 AM, Lou Cohen wrote:
>>>>
>>>>> Hello, all,
>>>>>
>>>>> I¹ve followed the many discussions about the emergence of
>>>>> QuteCsound
>>>>> and it
>>>>> appears I will making the jump from MacCsound soon, as I¹m about
>>>>> to
>>>>> purchase
>>>>> a new MacBook ‹ this is an Intel Mac with OSX10.5 pre-installed.
>>>>>
>>>>> Here¹s my dilemma:
>>>>>
>>>>> 1. I have a very large csd file that works well with MacCsound.
>>>>> There are
>>>>> about 3200 lines of code in the orchestra, and it monitors and
>>>>> responds to
>>>>> 325 widgets as well as incoming sound and computer keyboard
>>>>> activity.
>>>>>
>>>>> 2. To use MacCsound on an Intel machine it appears that I should
>>>>> install
>>>>> Csound 5.09, PPC version. I understand that 5.10 breaks MacCsound.
>>>>> However,
>>>>> checking Sourceforge, I do not see a version of 5.09 for OSX 10.5,
>>>>> only
>>>>> versions for 10.4. So it seems that I cannot consider moving
>>>>> MacCsound to my
>>>>> proposed new computer.
>>>>>
>>>>> 3. Therefore I must move to QuteCsound. The last time I tried my
>>>>> extensive
>>>>> body of code with QuteCsound it made too many demands on
>>>>> QuteCsound,
>>>>> but
>>>>> this was months ago, and of course in a different environment
>>>>> (PPC,
>>>>> OSX10.4,
>>>>> early version of QuteCsound.)
>>>>>
>>>>> 4. I cannot try QuteCsound on my current machine (PPC, OSX10.4)
>>>>> because
>>>>> QuteCsound requires Csound 5.10, and I don't dare install this
>>>>> while
>>>>> I'm
>>>>> depending on MacCsound on this machine.
>>>>>
>>>>> I don't know whether the world has changed enough for a transition
>>>>> to be
>>>>> possible. Does anyone have any information or advice?
>>>>>
>>>>> Thanks in advance for all the thoughtful responses I know will be
>>>>> coming.
>>>>>
>>>>> -Lou Cohen
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>> "unsubscribe csound"
>>>>
________________________________________________
Dr David Worrall.
- Experimental Polymedia: www.avatar.com.au
- Sonification: sonification.com.au
- Financial markets education: mindthemarkets.com.au
- MARCS Auditory Laboratories: marcs.uws.edu.au
|