Sorry, Csound uses SWIG to generate Python bindings, and SWIG is bound to a 
specific version of Python. So, currently Csound only works with Python 2.5.

When SWIG works with Python 3.0, I will change Csound to use Python 3.0. I 
haven't checked this yet, but I will do it next time I build Csound.

Thanks for the reminder,
Mike

----- Original Message ----- 
From: "Brent Boylan" 
To: 
Sent: Monday, February 16, 2009 11:30 PM
Subject: [Csnd] Re: Python and Csound


>
> Want to bring this thread back to the original topic: With the new version 
> of
> Python out, how long till it can be used with csound? py3k is said to be
> very backwards compatible. If csound wasn't looking for a specific version
> would it work 'straigth out of the box'? Or what if Python 3.01 was
> installed in a directory called python25?
>
>
> Caecos wrote:
>>
>> Is there a way to tell Csound where to find Python (i.e.: Python is
>> installed in another place than the standard C:\Python 2.5)?
>>
>
> -- 
> View this message in context: 
> http://www.nabble.com/Python-and--Csound-tp21522413p22050585.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound"
>