Hello everybody!

I've been using Csound for quite some time and decided to learn another
language to enhance its capabilities. My choice fell on Python, since it
seems to be supported best. (Are there other recommendations? May I ask,
what are the strong and weak points of each in respect to Csound?)

I would like to use Python3, which is the "shiny new thing", as stated by
the developers, more elegant and easier to learn. Probably also longer
lasting. My question is, does Csound support it yet? (And if not, when will
it?)

And is there a difference between calling Python code from Csound, and
calling Csound from a Python program, in respect to the Python versions?

Sorry for so many questions, but I haven't found this information nor on
csounds.com nor on other threads here in this forum.

Thanks in advance.

Eric

No, it depends on the package. Right now, we are at 2 something. It is
2.6 on Windows, probably on the others as well but might be another
2.x.

This will change when all the other Python goodies that composers use
with Csound also are easily available on 3.

Hope this helps,
Mike

On Mon, Aug 23, 2010 at 5:31 PM, Eric Luckerbau  wrote:
>
> Hello everybody!
>
> I've been using Csound for quite some time and decided to learn another
> language to enhance its capabilities. My choice fell on Python, since it
> seems to be supported best. (Are there other recommendations? May I ask,
> what are the strong and weak points of each in respect to Csound?)
>
> I would like to use Python3, which is the "shiny new thing", as stated by
> the developers, more elegant and easier to learn. Probably also longer
> lasting. My question is, does Csound support it yet? (And if not, when will
> it?)
>
> And is there a difference between calling Python code from Csound, and
> calling Csound from a Python program, in respect to the Python versions?
>
> Sorry for so many questions, but I haven't found this information nor on
> csounds.com nor on other threads here in this forum.
>
> Thanks in advance.
>
> Eric
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Does-Python3-work-with-Csound-tp2645361p2645361.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

We'll probably move to 3.0 when everybody else does too (scipy, pylab,  
etc). Currently released csound binaries use 2.6.

The main difference between python from csound and csound from python  
is that the former is designed to use Python to add some functionality  
to Csound, eg. for GUIs etc, whereas the latter allows for full  
applications to take advantage of Csound as a synthesis engine.

I would say Python is a good choice of a programming language to learn  
to use alongside Csound, but there are others.
Java/Processing seems to be quite popular too, for more interactive  
uses. Python is good too for algorithmic music.

Victor
On 23 Aug 2010, at 22:31, Eric Luckerbau wrote:

>
> Hello everybody!
>
> I've been using Csound for quite some time and decided to learn  
> another
> language to enhance its capabilities. My choice fell on Python,  
> since it
> seems to be supported best. (Are there other recommendations? May I  
> ask,
> what are the strong and weak points of each in respect to Csound?)
>
> I would like to use Python3, which is the "shiny new thing", as  
> stated by
> the developers, more elegant and easier to learn. Probably also longer
> lasting. My question is, does Csound support it yet? (And if not,  
> when will
> it?)
>
> And is there a difference between calling Python code from Csound, and
> calling Csound from a Python program, in respect to the Python  
> versions?
>
> Sorry for so many questions, but I haven't found this information  
> nor on
> csounds.com nor on other threads here in this forum.
>
> Thanks in advance.
>
> Eric
>
>
> -- 
> View this message in context: http://csound.1045644.n5.nabble.com/Does-Python3-work-with-Csound-tp2645361p2645361.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

(and python will have a prominent place in future QuteCsound releases)
((don't tell andrés - top secret!))

	=)


Am 23.08.2010 um 23:45 schrieb Victor Lazzarini:

> We'll probably move to 3.0 when everybody else does too (scipy,  
> pylab, etc). Currently released csound binaries use 2.6.
>
> The main difference between python from csound and csound from  
> python is that the former is designed to use Python to add some  
> functionality to Csound, eg. for GUIs etc, whereas the latter allows  
> for full applications to take advantage of Csound as a synthesis  
> engine.
>
> I would say Python is a good choice of a programming language to  
> learn to use alongside Csound, but there are others.
> Java/Processing seems to be quite popular too, for more interactive  
> uses. Python is good too for algorithmic music.
>
> Victor
> On 23 Aug 2010, at 22:31, Eric Luckerbau wrote:
>
>>
>> Hello everybody!
>>
>> I've been using Csound for quite some time and decided to learn  
>> another
>> language to enhance its capabilities. My choice fell on Python,  
>> since it
>> seems to be supported best. (Are there other recommendations? May I  
>> ask,
>> what are the strong and weak points of each in respect to Csound?)
>>
>> I would like to use Python3, which is the "shiny new thing", as  
>> stated by
>> the developers, more elegant and easier to learn. Probably also  
>> longer
>> lasting. My question is, does Csound support it yet? (And if not,  
>> when will
>> it?)
>>
>> And is there a difference between calling Python code from Csound,  
>> and
>> calling Csound from a Python program, in respect to the Python  
>> versions?
>>
>> Sorry for so many questions, but I haven't found this information  
>> nor on
>> csounds.com nor on other threads here in this forum.
>>
>> Thanks in advance.
>>
>> Eric
>>
>>
>> -- 
>> View this message in context: http://csound.1045644.n5.nabble.com/Does-Python3-work-with-Csound-tp2645361p2645361.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>> "unsubscribe csound"
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Not as far as I know. It's a little more refined. Ordered dictionaries
are nice, like STL maps.

On Mon, Aug 23, 2010 at 10:04 PM, Anthony Palomba
 wrote:
> Are there any new features in python3 that would make
> interfacing with csound better?
>
>
>
> -ap
>
>
>
> On Mon, Aug 23, 2010 at 4:48 PM, joachim heintz  wrote:
>>
>> (and python will have a prominent place in future QuteCsound releases)
>> ((don't tell andrés - top secret!))
>>
>>        =)
>>
>>
>> Am 23.08.2010 um 23:45 schrieb Victor Lazzarini:
>>
>>> We'll probably move to 3.0 when everybody else does too (scipy, pylab,
>>> etc). Currently released csound binaries use 2.6.
>>>
>>> The main difference between python from csound and csound from python is
>>> that the former is designed to use Python to add some functionality to
>>> Csound, eg. for GUIs etc, whereas the latter allows for full applications to
>>> take advantage of Csound as a synthesis engine.
>>>
>>> I would say Python is a good choice of a programming language to learn to
>>> use alongside Csound, but there are others.
>>> Java/Processing seems to be quite popular too, for more interactive uses.
>>> Python is good too for algorithmic music.
>>>
>>> Victor
>>> On 23 Aug 2010, at 22:31, Eric Luckerbau wrote:
>>>
>>>>
>>>> Hello everybody!
>>>>
>>>> I've been using Csound for quite some time and decided to learn another
>>>> language to enhance its capabilities. My choice fell on Python, since it
>>>> seems to be supported best. (Are there other recommendations? May I ask,
>>>> what are the strong and weak points of each in respect to Csound?)
>>>>
>>>> I would like to use Python3, which is the "shiny new thing", as stated
>>>> by
>>>> the developers, more elegant and easier to learn. Probably also longer
>>>> lasting. My question is, does Csound support it yet? (And if not, when
>>>> will
>>>> it?)
>>>>
>>>> And is there a difference between calling Python code from Csound, and
>>>> calling Csound from a Python program, in respect to the Python versions?
>>>>
>>>> Sorry for so many questions, but I haven't found this information nor on
>>>> csounds.com nor on other threads here in this forum.
>>>>
>>>> Thanks in advance.
>>>>
>>>> Eric
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://csound.1045644.n5.nabble.com/Does-Python3-work-with-Csound-tp2645361p2645361.html
>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

=)

If anyone wants to try it it's on svn, and it's a python interpreter
exposing most of QuteCsound (including widgets and event sheets) to
python. Still a work in progress but many things already work, and
feedback is most welcome...

Cheers,
Andrés

On Mon, Aug 23, 2010 at 10:48 PM, joachim heintz  wrote:
> (and python will have a prominent place in future QuteCsound releases)
> ((don't tell andrés - top secret!))
>
>        =)
>
>
> Am 23.08.2010 um 23:45 schrieb Victor Lazzarini:
>
>> We'll probably move to 3.0 when everybody else does too (scipy, pylab,
>> etc). Currently released csound binaries use 2.6.
>>
>> The main difference between python from csound and csound from python is
>> that the former is designed to use Python to add some functionality to
>> Csound, eg. for GUIs etc, whereas the latter allows for full applications to
>> take advantage of Csound as a synthesis engine.
>>
>> I would say Python is a good choice of a programming language to learn to
>> use alongside Csound, but there are others.
>> Java/Processing seems to be quite popular too, for more interactive uses.
>> Python is good too for algorithmic music.
>>
>> Victor
>> On 23 Aug 2010, at 22:31, Eric Luckerbau wrote:
>>
>>>
>>> Hello everybody!
>>>
>>> I've been using Csound for quite some time and decided to learn another
>>> language to enhance its capabilities. My choice fell on Python, since it
>>> seems to be supported best. (Are there other recommendations? May I ask,
>>> what are the strong and weak points of each in respect to Csound?)
>>>
>>> I would like to use Python3, which is the "shiny new thing", as stated by
>>> the developers, more elegant and easier to learn. Probably also longer
>>> lasting. My question is, does Csound support it yet? (And if not, when
>>> will
>>> it?)
>>>
>>> And is there a difference between calling Python code from Csound, and
>>> calling Csound from a Python program, in respect to the Python versions?
>>>
>>> Sorry for so many questions, but I haven't found this information nor on
>>> csounds.com nor on other threads here in this forum.
>>>
>>> Thanks in advance.
>>>
>>> Eric
>>>
>>>
>>> --
>>> View this message in context:
>>> http://csound.1045644.n5.nabble.com/Does-Python3-work-with-Csound-tp2645361p2645361.html
>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>



-- 


Andrés


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Does this mean all the present Python code will then have to be changed as
well, or will there be the option to compile Csound against the version you
want?

Anyway, Processing seems to be better suited for my needs than Python, so I
guess I'll first check out this one, thanks for the tip, I didn't know it so
far. (And there seems to be a good time to start, now that Csoundo is out.)

Eric

Hi Anthony,

Yes and yes.
It exposes most of QuteCsound so you will be able to modify and create
widgets from the interactive python interpreter, and its also a full
python interpreter, so you can run anything like matplotlib and numpy.
I also intend to expose things like ftables in a simple way (e.g. to
get a table as a numpy array, copy a python list into a table).

Cheers,
Andrés

On Tue, Aug 24, 2010 at 1:32 PM, Anthony Palomba  wrote:
> Andrés, what would exposing the QuteCsound UI allow me
> to do? Could I make my own UI? Would I be able to integrate
> something like matplotlib?
>
>
>
> -ap
>
>
>
>
>
>
> On Tue, Aug 24, 2010 at 3:46 AM, Andres Cabrera 
> wrote:
>>
>> =)
>>
>> If anyone wants to try it it's on svn, and it's a python interpreter
>> exposing most of QuteCsound (including widgets and event sheets) to
>> python. Still a work in progress but many things already work, and
>> feedback is most welcome...
>>
>> Cheers,
>> Andrés
>>
>> On Mon, Aug 23, 2010 at 10:48 PM, joachim heintz 
>> wrote:
>> > (and python will have a prominent place in future QuteCsound releases)
>> > ((don't tell andrés - top secret!))
>> >
>> >        =)
>> >
>> >
>> > Am 23.08.2010 um 23:45 schrieb Victor Lazzarini:
>> >
>> >> We'll probably move to 3.0 when everybody else does too (scipy, pylab,
>> >> etc). Currently released csound binaries use 2.6.
>> >>
>> >> The main difference between python from csound and csound from python
>> >> is
>> >> that the former is designed to use Python to add some functionality to
>> >> Csound, eg. for GUIs etc, whereas the latter allows for full
>> >> applications to
>> >> take advantage of Csound as a synthesis engine.
>> >>
>> >> I would say Python is a good choice of a programming language to learn
>> >> to
>> >> use alongside Csound, but there are others.
>> >> Java/Processing seems to be quite popular too, for more interactive
>> >> uses.
>> >> Python is good too for algorithmic music.
>> >>
>> >> Victor
>> >> On 23 Aug 2010, at 22:31, Eric Luckerbau wrote:
>> >>
>> >>>
>> >>> Hello everybody!
>> >>>
>> >>> I've been using Csound for quite some time and decided to learn
>> >>> another
>> >>> language to enhance its capabilities. My choice fell on Python, since
>> >>> it
>> >>> seems to be supported best. (Are there other recommendations? May I
>> >>> ask,
>> >>> what are the strong and weak points of each in respect to Csound?)
>> >>>
>> >>> I would like to use Python3, which is the "shiny new thing", as stated
>> >>> by
>> >>> the developers, more elegant and easier to learn. Probably also longer
>> >>> lasting. My question is, does Csound support it yet? (And if not, when
>> >>> will
>> >>> it?)
>> >>>
>> >>> And is there a difference between calling Python code from Csound, and
>> >>> calling Csound from a Python program, in respect to the Python
>> >>> versions?
>> >>>
>> >>> Sorry for so many questions, but I haven't found this information nor
>> >>> on
>> >>> csounds.com nor on other threads here in this forum.
>> >>>
>> >>> Thanks in advance.
>> >>>
>> >>> Eric
>> >>>
>> >>>
>> >>> --
>> >>> View this message in context:
>> >>>
>> >>> http://csound.1045644.n5.nabble.com/Does-Python3-work-with-Csound-tp2645361p2645361.html
>> >>> Sent from the Csound - General mailing list archive at Nabble.com.
>> >>>
>> >>>
>> >>> Send bugs reports to the Sourceforge bug tracker
>> >>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> >>> Discussions of bugs and features can be posted here
>> >>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >>> "unsubscribe
>> >>> csound"
>> >>>
>> >>
>> >>
>> >>
>> >> Send bugs reports to the Sourceforge bug tracker
>> >>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> >> Discussions of bugs and features can be posted here
>> >> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >> "unsubscribe
>> >> csound"
>> >>
>> >>
>> >
>> >
>> >
>> > Send bugs reports to the Sourceforge bug tracker
>> >           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> > Discussions of bugs and features can be posted here
>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> > csound"
>> >
>> >
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>



-- 


Andrés


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

That sounds really good. Isn't it the time to find a better and more  
suitable name to this software? ;)

Victor
On 24 Aug 2010, at 15:41, Andres Cabrera wrote:

> Hi Anthony,
>
> Yes and yes.
> It exposes most of QuteCsound so you will be able to modify and create
> widgets from the interactive python interpreter, and its also a full
> python interpreter, so you can run anything like matplotlib and numpy.
> I also intend to expose things like ftables in a simple way (e.g. to
> get a table as a numpy array, copy a python list into a table).
>
> Cheers,
> Andrés
>
> On Tue, Aug 24, 2010 at 1:32 PM, Anthony Palomba  > wrote:
>> Andrés, what would exposing the QuteCsound UI allow me
>> to do? Could I make my own UI? Would I be able to integrate
>> something like matplotlib?
>>
>>
>>
>> -ap
>>
>>
>>
>>
>>
>>
>> On Tue, Aug 24, 2010 at 3:46 AM, Andres Cabrera > >
>> wrote:
>>>
>>> =)
>>>
>>> If anyone wants to try it it's on svn, and it's a python interpreter
>>> exposing most of QuteCsound (including widgets and event sheets) to
>>> python. Still a work in progress but many things already work, and
>>> feedback is most welcome...
>>>
>>> Cheers,
>>> Andrés
>>>
>>> On Mon, Aug 23, 2010 at 10:48 PM, joachim heintz >> >
>>> wrote:
>>>> (and python will have a prominent place in future QuteCsound  
>>>> releases)
>>>> ((don't tell andrés - top secret!))
>>>>
>>>>        =)
>>>>
>>>>
>>>> Am 23.08.2010 um 23:45 schrieb Victor Lazzarini:
>>>>
>>>>> We'll probably move to 3.0 when everybody else does too (scipy,  
>>>>> pylab,
>>>>> etc). Currently released csound binaries use 2.6.
>>>>>
>>>>> The main difference between python from csound and csound from  
>>>>> python
>>>>> is
>>>>> that the former is designed to use Python to add some  
>>>>> functionality to
>>>>> Csound, eg. for GUIs etc, whereas the latter allows for full
>>>>> applications to
>>>>> take advantage of Csound as a synthesis engine.
>>>>>
>>>>> I would say Python is a good choice of a programming language to  
>>>>> learn
>>>>> to
>>>>> use alongside Csound, but there are others.
>>>>> Java/Processing seems to be quite popular too, for more  
>>>>> interactive
>>>>> uses.
>>>>> Python is good too for algorithmic music.
>>>>>
>>>>> Victor
>>>>> On 23 Aug 2010, at 22:31, Eric Luckerbau wrote:
>>>>>
>>>>>>
>>>>>> Hello everybody!
>>>>>>
>>>>>> I've been using Csound for quite some time and decided to learn
>>>>>> another
>>>>>> language to enhance its capabilities. My choice fell on Python,  
>>>>>> since
>>>>>> it
>>>>>> seems to be supported best. (Are there other recommendations?  
>>>>>> May I
>>>>>> ask,
>>>>>> what are the strong and weak points of each in respect to  
>>>>>> Csound?)
>>>>>>
>>>>>> I would like to use Python3, which is the "shiny new thing", as  
>>>>>> stated
>>>>>> by
>>>>>> the developers, more elegant and easier to learn. Probably also  
>>>>>> longer
>>>>>> lasting. My question is, does Csound support it yet? (And if  
>>>>>> not, when
>>>>>> will
>>>>>> it?)
>>>>>>
>>>>>> And is there a difference between calling Python code from  
>>>>>> Csound, and
>>>>>> calling Csound from a Python program, in respect to the Python
>>>>>> versions?
>>>>>>
>>>>>> Sorry for so many questions, but I haven't found this  
>>>>>> information nor
>>>>>> on
>>>>>> csounds.com nor on other threads here in this forum.
>>>>>>
>>>>>> Thanks in advance.
>>>>>>
>>>>>> Eric
>>>>>>
>>>>>>
>>>>>> --
>>>>>> View this message in context:
>>>>>>
>>>>>> http://csound.1045644.n5.nabble.com/Does-Python3-work-with-Csound-tp2645361p2645361.html
>>>>>> Sent from the Csound - General mailing list archive at  
>>>>>> Nabble.com.
>>>>>>
>>>>>>
>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>> Discussions of bugs and features can be posted here
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>> "unsubscribe
>>>>>> csound"
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> Discussions of bugs and features can be posted here
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>> "unsubscribe
>>>>> csound"
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>>>> "unsubscribe
>>>> csound"
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>> Andrés
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>>> "unsubscribe
>>> csound"
>>>
>>
>>
>
>
>
> -- 
>
>
> Andrés
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I agree that it is more than a "cute" little "thing".  It is MAJOR and HUGE and SUPER IMPORTANT. and quite "huge".

-dB

On Aug 24, 2010, at 10:50 AM, Victor Lazzarini wrote:

> That sounds really good. Isn't it the time to find a better and more suitable name to this software? ;)
> 
> Victor
> On 24 Aug 2010, at 15:41, Andres Cabrera wrote:
> 
>> Hi Anthony,
>> 
>> Yes and yes.
>> It exposes most of QuteCsound so you will be able to modify and create
>> widgets from the interactive python interpreter, and its also a full
>> python interpreter, so you can run anything like matplotlib and numpy.
>> I also intend to expose things like ftables in a simple way (e.g. to
>> get a table as a numpy array, copy a python list into a table).
>> 
>> Cheers,
>> Andrés
>> 
>> On Tue, Aug 24, 2010 at 1:32 PM, Anthony Palomba  wrote:
>>> Andrés, what would exposing the QuteCsound UI allow me
>>> to do? Could I make my own UI? Would I be able to integrate
>>> something like matplotlib?
>>> 
>>> 
>>> 
>>> -ap
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Tue, Aug 24, 2010 at 3:46 AM, Andres Cabrera 
>>> wrote:
>>>> 
>>>> =)
>>>> 
>>>> If anyone wants to try it it's on svn, and it's a python interpreter
>>>> exposing most of QuteCsound (including widgets and event sheets) to
>>>> python. Still a work in progress but many things already work, and
>>>> feedback is most welcome...
>>>> 
>>>> Cheers,
>>>> Andrés
>>>> 
>>>> On Mon, Aug 23, 2010 at 10:48 PM, joachim heintz 
>>>> wrote:
>>>>> (and python will have a prominent place in future QuteCsound releases)
>>>>> ((don't tell andrés - top secret!))
>>>>> 
>>>>>       =)
>>>>> 
>>>>> 
>>>>> Am 23.08.2010 um 23:45 schrieb Victor Lazzarini:
>>>>> 
>>>>>> We'll probably move to 3.0 when everybody else does too (scipy, pylab,
>>>>>> etc). Currently released csound binaries use 2.6.
>>>>>> 
>>>>>> The main difference between python from csound and csound from python
>>>>>> is
>>>>>> that the former is designed to use Python to add some functionality to
>>>>>> Csound, eg. for GUIs etc, whereas the latter allows for full
>>>>>> applications to
>>>>>> take advantage of Csound as a synthesis engine.
>>>>>> 
>>>>>> I would say Python is a good choice of a programming language to learn
>>>>>> to
>>>>>> use alongside Csound, but there are others.
>>>>>> Java/Processing seems to be quite popular too, for more interactive
>>>>>> uses.
>>>>>> Python is good too for algorithmic music.
>>>>>> 
>>>>>> Victor
>>>>>> On 23 Aug 2010, at 22:31, Eric Luckerbau wrote:
>>>>>> 
>>>>>>> 
>>>>>>> Hello everybody!
>>>>>>> 
>>>>>>> I've been using Csound for quite some time and decided to learn
>>>>>>> another
>>>>>>> language to enhance its capabilities. My choice fell on Python, since
>>>>>>> it
>>>>>>> seems to be supported best. (Are there other recommendations? May I
>>>>>>> ask,
>>>>>>> what are the strong and weak points of each in respect to Csound?)
>>>>>>> 
>>>>>>> I would like to use Python3, which is the "shiny new thing", as stated
>>>>>>> by
>>>>>>> the developers, more elegant and easier to learn. Probably also longer
>>>>>>> lasting. My question is, does Csound support it yet? (And if not, when
>>>>>>> will
>>>>>>> it?)
>>>>>>> 
>>>>>>> And is there a difference between calling Python code from Csound, and
>>>>>>> calling Csound from a Python program, in respect to the Python
>>>>>>> versions?
>>>>>>> 
>>>>>>> Sorry for so many questions, but I haven't found this information nor
>>>>>>> on
>>>>>>> csounds.com nor on other threads here in this forum.
>>>>>>> 
>>>>>>> Thanks in advance.
>>>>>>> 
>>>>>>> Eric
>>>>>>> 
>>>>>>> 
>>>>>>> --
>>>>>>> View this message in context:
>>>>>>> 
>>>>>>> http://csound.1045644.n5.nabble.com/Does-Python3-work-with-Csound-tp2645361p2645361.html
>>>>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>>>>> 
>>>>>>> 
>>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>>         https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>> "unsubscribe
>>>>>>> csound"
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>         https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>> Discussions of bugs and features can be posted here
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>> "unsubscribe
>>>>>> csound"
>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> Discussions of bugs and features can be posted here
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>>> csound"
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> 
>>>> 
>>>> Andrés
>>>> 
>>>> 
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>> 
>>> 
>>> 
>> 
>> 
>> 
>> -- 
>> 
>> 
>> Andrés
>> 
>> 
>> Send bugs reports to the Sourceforge bug tracker
>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>> 
> 
> 
> 
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Yes, I know... at least it is a memorable name... =)

Cheers,
Andrés

On Tue, Aug 24, 2010 at 3:50 PM, Victor Lazzarini
 wrote:
> That sounds really good. Isn't it the time to find a better and more
> suitable name to this software? ;)
>
> Victor
> On 24 Aug 2010, at 15:41, Andres Cabrera wrote:
>
>> Hi Anthony,
>>
>> Yes and yes.
>> It exposes most of QuteCsound so you will be able to modify and create
>> widgets from the interactive python interpreter, and its also a full
>> python interpreter, so you can run anything like matplotlib and numpy.
>> I also intend to expose things like ftables in a simple way (e.g. to
>> get a table as a numpy array, copy a python list into a table).
>>
>> Cheers,
>> Andrés
>>
>> On Tue, Aug 24, 2010 at 1:32 PM, Anthony Palomba 
>> wrote:
>>>
>>> Andrés, what would exposing the QuteCsound UI allow me
>>> to do? Could I make my own UI? Would I be able to integrate
>>> something like matplotlib?
>>>
>>>
>>>
>>> -ap
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Aug 24, 2010 at 3:46 AM, Andres Cabrera 
>>> wrote:
>>>>
>>>> =)
>>>>
>>>> If anyone wants to try it it's on svn, and it's a python interpreter
>>>> exposing most of QuteCsound (including widgets and event sheets) to
>>>> python. Still a work in progress but many things already work, and
>>>> feedback is most welcome...
>>>>
>>>> Cheers,
>>>> Andrés
>>>>
>>>> On Mon, Aug 23, 2010 at 10:48 PM, joachim heintz 
>>>> wrote:
>>>>>
>>>>> (and python will have a prominent place in future QuteCsound releases)
>>>>> ((don't tell andrés - top secret!))
>>>>>
>>>>>       =)
>>>>>
>>>>>
>>>>> Am 23.08.2010 um 23:45 schrieb Victor Lazzarini:
>>>>>
>>>>>> We'll probably move to 3.0 when everybody else does too (scipy, pylab,
>>>>>> etc). Currently released csound binaries use 2.6.
>>>>>>
>>>>>> The main difference between python from csound and csound from python
>>>>>> is
>>>>>> that the former is designed to use Python to add some functionality to
>>>>>> Csound, eg. for GUIs etc, whereas the latter allows for full
>>>>>> applications to
>>>>>> take advantage of Csound as a synthesis engine.
>>>>>>
>>>>>> I would say Python is a good choice of a programming language to learn
>>>>>> to
>>>>>> use alongside Csound, but there are others.
>>>>>> Java/Processing seems to be quite popular too, for more interactive
>>>>>> uses.
>>>>>> Python is good too for algorithmic music.
>>>>>>
>>>>>> Victor
>>>>>> On 23 Aug 2010, at 22:31, Eric Luckerbau wrote:
>>>>>>
>>>>>>>
>>>>>>> Hello everybody!
>>>>>>>
>>>>>>> I've been using Csound for quite some time and decided to learn
>>>>>>> another
>>>>>>> language to enhance its capabilities. My choice fell on Python, since
>>>>>>> it
>>>>>>> seems to be supported best. (Are there other recommendations? May I
>>>>>>> ask,
>>>>>>> what are the strong and weak points of each in respect to Csound?)
>>>>>>>
>>>>>>> I would like to use Python3, which is the "shiny new thing", as
>>>>>>> stated
>>>>>>> by
>>>>>>> the developers, more elegant and easier to learn. Probably also
>>>>>>> longer
>>>>>>> lasting. My question is, does Csound support it yet? (And if not,
>>>>>>> when
>>>>>>> will
>>>>>>> it?)
>>>>>>>
>>>>>>> And is there a difference between calling Python code from Csound,
>>>>>>> and
>>>>>>> calling Csound from a Python program, in respect to the Python
>>>>>>> versions?
>>>>>>>
>>>>>>> Sorry for so many questions, but I haven't found this information nor
>>>>>>> on
>>>>>>> csounds.com nor on other threads here in this forum.
>>>>>>>
>>>>>>> Thanks in advance.
>>>>>>>
>>>>>>> Eric
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> View this message in context:
>>>>>>>
>>>>>>>
>>>>>>> http://csound.1045644.n5.nabble.com/Does-Python3-work-with-Csound-tp2645361p2645361.html
>>>>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>>>>>
>>>>>>>
>>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>>         https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>> "unsubscribe
>>>>>>> csound"
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>         https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>> Discussions of bugs and features can be posted here
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>> "unsubscribe
>>>>>> csound"
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> Discussions of bugs and features can be posted here
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>> "unsubscribe
>>>>> csound"
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Andrés
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>>
>>>
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>



-- 


Andrés


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi,

Yes, you can try it know if you build from svn, but I think it's only
working on Linux for now, and it's still very much a work in progress,
bound to change.
No examples or documentation yet, though...

Cheers,
Andrés

On Tue, Aug 24, 2010 at 3:55 PM, Anthony Palomba  wrote:
> Sweet, is this available now? Do you have any examples
> that integrate Matplotlib? That would fantastic!
>
>
>
> -ap
>
>
>
>
>
>
>
>
> On Tue, Aug 24, 2010 at 9:41 AM, Andres Cabrera 
> wrote:
>>
>> Hi Anthony,
>>
>> Yes and yes.
>> It exposes most of QuteCsound so you will be able to modify and create
>> widgets from the interactive python interpreter, and its also a full
>> python interpreter, so you can run anything like matplotlib and numpy.
>> I also intend to expose things like ftables in a simple way (e.g. to
>> get a table as a numpy array, copy a python list into a table).
>>
>> Cheers,
>> Andrés
>>
>> On Tue, Aug 24, 2010 at 1:32 PM, Anthony Palomba 
>> wrote:
>> > Andrés, what would exposing the QuteCsound UI allow me
>> > to do? Could I make my own UI? Would I be able to integrate
>> > something like matplotlib?
>> >
>> >
>> >
>> > -ap
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Tue, Aug 24, 2010 at 3:46 AM, Andres Cabrera 
>> > wrote:
>> >>
>> >> =)
>> >>
>> >> If anyone wants to try it it's on svn, and it's a python interpreter
>> >> exposing most of QuteCsound (including widgets and event sheets) to
>> >> python. Still a work in progress but many things already work, and
>> >> feedback is most welcome...
>> >>
>> >> Cheers,
>> >> Andrés
>> >>
>> >> On Mon, Aug 23, 2010 at 10:48 PM, joachim heintz 
>> >> wrote:
>> >> > (and python will have a prominent place in future QuteCsound
>> >> > releases)
>> >> > ((don't tell andrés - top secret!))
>> >> >
>> >> >        =)
>> >> >
>> >> >
>> >> > Am 23.08.2010 um 23:45 schrieb Victor Lazzarini:
>> >> >
>> >> >> We'll probably move to 3.0 when everybody else does too (scipy,
>> >> >> pylab,
>> >> >> etc). Currently released csound binaries use 2.6.
>> >> >>
>> >> >> The main difference between python from csound and csound from
>> >> >> python
>> >> >> is
>> >> >> that the former is designed to use Python to add some functionality
>> >> >> to
>> >> >> Csound, eg. for GUIs etc, whereas the latter allows for full
>> >> >> applications to
>> >> >> take advantage of Csound as a synthesis engine.
>> >> >>
>> >> >> I would say Python is a good choice of a programming language to
>> >> >> learn
>> >> >> to
>> >> >> use alongside Csound, but there are others.
>> >> >> Java/Processing seems to be quite popular too, for more interactive
>> >> >> uses.
>> >> >> Python is good too for algorithmic music.
>> >> >>
>> >> >> Victor
>> >> >> On 23 Aug 2010, at 22:31, Eric Luckerbau wrote:
>> >> >>
>> >> >>>
>> >> >>> Hello everybody!
>> >> >>>
>> >> >>> I've been using Csound for quite some time and decided to learn
>> >> >>> another
>> >> >>> language to enhance its capabilities. My choice fell on Python,
>> >> >>> since
>> >> >>> it
>> >> >>> seems to be supported best. (Are there other recommendations? May I
>> >> >>> ask,
>> >> >>> what are the strong and weak points of each in respect to Csound?)
>> >> >>>
>> >> >>> I would like to use Python3, which is the "shiny new thing", as
>> >> >>> stated
>> >> >>> by
>> >> >>> the developers, more elegant and easier to learn. Probably also
>> >> >>> longer
>> >> >>> lasting. My question is, does Csound support it yet? (And if not,
>> >> >>> when
>> >> >>> will
>> >> >>> it?)
>> >> >>>
>> >> >>> And is there a difference between calling Python code from Csound,
>> >> >>> and
>> >> >>> calling Csound from a Python program, in respect to the Python
>> >> >>> versions?
>> >> >>>
>> >> >>> Sorry for so many questions, but I haven't found this information
>> >> >>> nor
>> >> >>> on
>> >> >>> csounds.com nor on other threads here in this forum.
>> >> >>>
>> >> >>> Thanks in advance.
>> >> >>>
>> >> >>> Eric
>> >> >>>
>> >> >>>
>> >> >>> --
>> >> >>> View this message in context:
>> >> >>>
>> >> >>>
>> >> >>> http://csound.1045644.n5.nabble.com/Does-Python3-work-with-Csound-tp2645361p2645361.html
>> >> >>> Sent from the Csound - General mailing list archive at Nabble.com.
>> >> >>>
>> >> >>>
>> >> >>> Send bugs reports to the Sourceforge bug tracker
>> >> >>>
>> >> >>>  https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> >> >>> Discussions of bugs and features can be posted here
>> >> >>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >> >>> "unsubscribe
>> >> >>> csound"
>> >> >>>
>> >> >>
>> >> >>
>> >> >>
>> >> >> Send bugs reports to the Sourceforge bug tracker
>> >> >>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> >> >> Discussions of bugs and features can be posted here
>> >> >> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >> >> "unsubscribe
>> >> >> csound"
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > Send bugs reports to the Sourceforge bug tracker
>> >> >           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> >> > Discussions of bugs and features can be posted here
>> >> > To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >> > "unsubscribe
>> >> > csound"
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >>
>> >>
>> >> Andrés
>> >>
>> >>
>> >> Send bugs reports to the Sourceforge bug tracker
>> >>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> >> Discussions of bugs and features can be posted here
>> >> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >> "unsubscribe
>> >> csound"
>> >>
>> >
>> >
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>



-- 


Andrés


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

PyCSound ? PySound? :-)

Sounds cool really.

2010/8/24 Victor Lazzarini :
> That sounds really good. Isn't it the time to find a better and more
> suitable name to this software? ;)
>
> Victor
> On 24 Aug 2010, at 15:41, Andres Cabrera wrote:
>
>> Hi Anthony,
>>
>> Yes and yes.
>> It exposes most of QuteCsound so you will be able to modify and create
>> widgets from the interactive python interpreter, and its also a full
>> python interpreter, so you can run anything like matplotlib and numpy.
>> I also intend to expose things like ftables in a simple way (e.g. to
>> get a table as a numpy array, copy a python list into a table).
>>
>> Cheers,
>> Andrés
>>
>> On Tue, Aug 24, 2010 at 1:32 PM, Anthony Palomba 
>> wrote:
>>>
>>> Andrés, what would exposing the QuteCsound UI allow me
>>> to do? Could I make my own UI? Would I be able to integrate
>>> something like matplotlib?
>>>
>>>
>>>
>>> -ap
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Aug 24, 2010 at 3:46 AM, Andres Cabrera 
>>> wrote:
>>>>
>>>> =)
>>>>
>>>> If anyone wants to try it it's on svn, and it's a python interpreter
>>>> exposing most of QuteCsound (including widgets and event sheets) to
>>>> python. Still a work in progress but many things already work, and
>>>> feedback is most welcome...
>>>>
>>>> Cheers,
>>>> Andrés
>>>>
>>>> On Mon, Aug 23, 2010 at 10:48 PM, joachim heintz 
>>>> wrote:
>>>>>
>>>>> (and python will have a prominent place in future QuteCsound releases)
>>>>> ((don't tell andrés - top secret!))
>>>>>
>>>>>       =)
>>>>>
>>>>>
>>>>> Am 23.08.2010 um 23:45 schrieb Victor Lazzarini:
>>>>>
>>>>>> We'll probably move to 3.0 when everybody else does too (scipy, pylab,
>>>>>> etc). Currently released csound binaries use 2.6.
>>>>>>
>>>>>> The main difference between python from csound and csound from python
>>>>>> is
>>>>>> that the former is designed to use Python to add some functionality to
>>>>>> Csound, eg. for GUIs etc, whereas the latter allows for full
>>>>>> applications to
>>>>>> take advantage of Csound as a synthesis engine.
>>>>>>
>>>>>> I would say Python is a good choice of a programming language to learn
>>>>>> to
>>>>>> use alongside Csound, but there are others.
>>>>>> Java/Processing seems to be quite popular too, for more interactive
>>>>>> uses.
>>>>>> Python is good too for algorithmic music.
>>>>>>
>>>>>> Victor
>>>>>> On 23 Aug 2010, at 22:31, Eric Luckerbau wrote:
>>>>>>
>>>>>>>
>>>>>>> Hello everybody!
>>>>>>>
>>>>>>> I've been using Csound for quite some time and decided to learn
>>>>>>> another
>>>>>>> language to enhance its capabilities. My choice fell on Python, since
>>>>>>> it
>>>>>>> seems to be supported best. (Are there other recommendations? May I
>>>>>>> ask,
>>>>>>> what are the strong and weak points of each in respect to Csound?)
>>>>>>>
>>>>>>> I would like to use Python3, which is the "shiny new thing", as
>>>>>>> stated
>>>>>>> by
>>>>>>> the developers, more elegant and easier to learn. Probably also
>>>>>>> longer
>>>>>>> lasting. My question is, does Csound support it yet? (And if not,
>>>>>>> when
>>>>>>> will
>>>>>>> it?)
>>>>>>>
>>>>>>> And is there a difference between calling Python code from Csound,
>>>>>>> and
>>>>>>> calling Csound from a Python program, in respect to the Python
>>>>>>> versions?
>>>>>>>
>>>>>>> Sorry for so many questions, but I haven't found this information nor
>>>>>>> on
>>>>>>> csounds.com nor on other threads here in this forum.
>>>>>>>
>>>>>>> Thanks in advance.
>>>>>>>
>>>>>>> Eric
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> View this message in context:
>>>>>>>
>>>>>>>
>>>>>>> http://csound.1045644.n5.nabble.com/Does-Python3-work-with-Csound-tp2645361p2645361.html
>>>>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>>>>>
>>>>>>>
>>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>>         https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>> "unsubscribe
>>>>>>> csound"
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>         https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>> Discussions of bugs and features can be posted here
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>> "unsubscribe
>>>>>> csound"
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> Discussions of bugs and features can be posted here
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>> "unsubscribe
>>>>> csound"
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Andrés
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>>
>>>
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I think you should name it after Dima.

http://csound.1045644.n5.nabble.com/QuteCsound-premier-prix-td1102802.html#a1102803

;-)

.mmb

On 8/24/10 12:08 PM, Andres Cabrera wrote:
> Yes, I know... at least it is a memorable name... =)
>
> Cheers,
> Andrés
>
> On Tue, Aug 24, 2010 at 3:50 PM, Victor Lazzarini
>   wrote:
>    
>> That sounds really good. Isn't it the time to find a better and more
>> suitable name to this software? ;)
>>
>> Victor
>> On 24 Aug 2010, at 15:41, Andres Cabrera wrote:
>>
>>      
>>> Hi Anthony,
>>>
>>> Yes and yes.
>>> It exposes most of QuteCsound so you will be able to modify and create
>>> widgets from the interactive python interpreter, and its also a full
>>> python interpreter, so you can run anything like matplotlib and numpy.
>>> I also intend to expose things like ftables in a simple way (e.g. to
>>> get a table as a numpy array, copy a python list into a table).
>>>
>>> Cheers,
>>> Andrés
>>>
>>> On Tue, Aug 24, 2010 at 1:32 PM, Anthony Palomba
>>> wrote:
>>>        
>>>> Andrés, what would exposing the QuteCsound UI allow me
>>>> to do? Could I make my own UI? Would I be able to integrate
>>>> something like matplotlib?
>>>>
>>>>
>>>>
>>>> -ap
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, Aug 24, 2010 at 3:46 AM, Andres Cabrera
>>>> wrote:
>>>>          
>>>>> =)
>>>>>
>>>>> If anyone wants to try it it's on svn, and it's a python interpreter
>>>>> exposing most of QuteCsound (including widgets and event sheets) to
>>>>> python. Still a work in progress but many things already work, and
>>>>> feedback is most welcome...
>>>>>
>>>>> Cheers,
>>>>> Andrés
>>>>>
>>>>> On Mon, Aug 23, 2010 at 10:48 PM, joachim heintz
>>>>> wrote:
>>>>>            
>>>>>> (and python will have a prominent place in future QuteCsound releases)
>>>>>> ((don't tell andrés - top secret!))
>>>>>>
>>>>>>        =)
>>>>>>
>>>>>>
>>>>>> Am 23.08.2010 um 23:45 schrieb Victor Lazzarini:
>>>>>>
>>>>>>              
>>>>>>> We'll probably move to 3.0 when everybody else does too (scipy, pylab,
>>>>>>> etc). Currently released csound binaries use 2.6.
>>>>>>>
>>>>>>> The main difference between python from csound and csound from python
>>>>>>> is
>>>>>>> that the former is designed to use Python to add some functionality to
>>>>>>> Csound, eg. for GUIs etc, whereas the latter allows for full
>>>>>>> applications to
>>>>>>> take advantage of Csound as a synthesis engine.
>>>>>>>
>>>>>>> I would say Python is a good choice of a programming language to learn
>>>>>>> to
>>>>>>> use alongside Csound, but there are others.
>>>>>>> Java/Processing seems to be quite popular too, for more interactive
>>>>>>> uses.
>>>>>>> Python is good too for algorithmic music.
>>>>>>>
>>>>>>> Victor
>>>>>>> On 23 Aug 2010, at 22:31, Eric Luckerbau wrote:
>>>>>>>
>>>>>>>                
>>>>>>>> Hello everybody!
>>>>>>>>
>>>>>>>> I've been using Csound for quite some time and decided to learn
>>>>>>>> another
>>>>>>>> language to enhance its capabilities. My choice fell on Python, since
>>>>>>>> it
>>>>>>>> seems to be supported best. (Are there other recommendations? May I
>>>>>>>> ask,
>>>>>>>> what are the strong and weak points of each in respect to Csound?)
>>>>>>>>
>>>>>>>> I would like to use Python3, which is the "shiny new thing", as
>>>>>>>> stated
>>>>>>>> by
>>>>>>>> the developers, more elegant and easier to learn. Probably also
>>>>>>>> longer
>>>>>>>> lasting. My question is, does Csound support it yet? (And if not,
>>>>>>>> when
>>>>>>>> will
>>>>>>>> it?)
>>>>>>>>
>>>>>>>> And is there a difference between calling Python code from Csound,
>>>>>>>> and
>>>>>>>> calling Csound from a Python program, in respect to the Python
>>>>>>>> versions?
>>>>>>>>
>>>>>>>> Sorry for so many questions, but I haven't found this information nor
>>>>>>>> on
>>>>>>>> csounds.com nor on other threads here in this forum.
>>>>>>>>
>>>>>>>> Thanks in advance.
>>>>>>>>
>>>>>>>> Eric
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> View this message in context:
>>>>>>>>
>>>>>>>>
>>>>>>>> http://csound.1045644.n5.nabble.com/Does-Python3-work-with-Csound-tp2645361p2645361.html
>>>>>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>>>>>>
>>>>>>>>
>>>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>>> "unsubscribe
>>>>>>>> csound"
>>>>>>>>
>>>>>>>>                  
>>>>>>>
>>>>>>>
>>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>> "unsubscribe
>>>>>>> csound"
>>>>>>>
>>>>>>>
>>>>>>>                
>>>>>>
>>>>>>
>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>> Discussions of bugs and features can be posted here
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>> "unsubscribe
>>>>>> csound"
>>>>>>
>>>>>>
>>>>>>              
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> Andrés
>>>>>
>>>>>
>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> Discussions of bugs and features can be posted here
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>>> csound"
>>>>>
>>>>>            
>>>>
>>>>          
>>>
>>>
>>> --
>>>
>>>
>>> Andrés
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>        
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>>      
>
>
>    



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"