I'm running, in QuteCsound 0.50 on MacOS 10.5.8, the ultra-basic Python
examples from issue 6 of the Csound Journal.

I seem to have both Python 2.6 and Python 3.0 on this computer. (I never use
them, but they're in Applications.) I don't know which one QuteCsound would
be invoking. There doesn't seem to be a QuteCsound Configure selection for
that, but one of them pretty much has to be getting invoked, because
otherwise the py.. opcodes would cause errors.

The QuteCsound documentation pane shows Csound 5.12, so I'm guessing that's
what is running.

In any event, the Python code .csd runs without error messages, but the
pyruni print statements don't print anything to the QuteCsound Output
Console pane. From the Csound Journal article, I would expect that there
would be text printing out to that pane. Am I just not understanding what's
supposed to happen? Or does QuteCsound shunt the Python print statements off
somewhere to a different output stream that never shows up?

Sorry to be so dense about this. If I used these tools every day, or even
every week, I'd be further along. Thanks for any help or insight you can
offer!

--Jim Aikin

Python opcodes will use the Apple supplied Python 2.5.

There seems to be a problem with the python opcodes on OSX. I just  
tried one example and it's
crashing. Not sure why now.

Regards

Victor
On 1 May 2010, at 08:02, Jim Aikin wrote:

>
> I'm running, in QuteCsound 0.50 on MacOS 10.5.8, the ultra-basic  
> Python
> examples from issue 6 of the Csound Journal.
>
> I seem to have both Python 2.6 and Python 3.0 on this computer. (I  
> never use
> them, but they're in Applications.) I don't know which one  
> QuteCsound would
> be invoking. There doesn't seem to be a QuteCsound Configure  
> selection for
> that, but one of them pretty much has to be getting invoked, because
> otherwise the py.. opcodes would cause errors.
>
> The QuteCsound documentation pane shows Csound 5.12, so I'm guessing  
> that's
> what is running.
>
> In any event, the Python code .csd runs without error messages, but  
> the
> pyruni print statements don't print anything to the QuteCsound Output
> Console pane. From the Csound Journal article, I would expect that  
> there
> would be text printing out to that pane. Am I just not understanding  
> what's
> supposed to happen? Or does QuteCsound shunt the Python print  
> statements off
> somewhere to a different output stream that never shows up?
>
> Sorry to be so dense about this. If I used these tools every day, or  
> even
> every week, I'd be further along. Thanks for any help or insight you  
> can
> offer!
>
> --Jim Aikin
> -- 
> View this message in context: http://old.nabble.com/Python-in-QuteCsound-tp28419160p28419160.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"

Sorry, I was wrong. It was something else that was crashing csound,  
nothing to do with the python opcodes. These seem to run OK, but I get

QUTECSOUND: Message buffer overflow. Messages discarded!

If you 'Run in Term', you'll get all the messages.

Victor


On 1 May 2010, at 08:20, Victor Lazzarini wrote:

> Python opcodes will use the Apple supplied Python 2.5.
>
> There seems to be a problem with the python opcodes on OSX. I just  
> tried one example and it's
> crashing. Not sure why now.
>
> Regards
>
> Victor
> On 1 May 2010, at 08:02, Jim Aikin wrote:
>
>>
>> I'm running, in QuteCsound 0.50 on MacOS 10.5.8, the ultra-basic  
>> Python
>> examples from issue 6 of the Csound Journal.
>>
>> I seem to have both Python 2.6 and Python 3.0 on this computer. (I  
>> never use
>> them, but they're in Applications.) I don't know which one  
>> QuteCsound would
>> be invoking. There doesn't seem to be a QuteCsound Configure  
>> selection for
>> that, but one of them pretty much has to be getting invoked, because
>> otherwise the py.. opcodes would cause errors.
>>
>> The QuteCsound documentation pane shows Csound 5.12, so I'm  
>> guessing that's
>> what is running.
>>
>> In any event, the Python code .csd runs without error messages, but  
>> the
>> pyruni print statements don't print anything to the QuteCsound Output
>> Console pane. From the Csound Journal article, I would expect that  
>> there
>> would be text printing out to that pane. Am I just not  
>> understanding what's
>> supposed to happen? Or does QuteCsound shunt the Python print  
>> statements off
>> somewhere to a different output stream that never shows up?
>>
>> Sorry to be so dense about this. If I used these tools every day,  
>> or even
>> every week, I'd be further along. Thanks for any help or insight  
>> you can
>> offer!
>>
>> --Jim Aikin
>> -- 
>> View this message in context: http://old.nabble.com/Python-in-QuteCsound-tp28419160p28419160.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"

Hmm. Sounds like it's a bug in QuteCsound, then.

I don't actually care about the message output. I was just testing to see if
the Python implementation was working. I'll have to test further to see if
QuteCsound can handle stuff that I might actually want to do with Python....


Victor Lazzarini wrote:
> 
> Sorry, I was wrong. It was something else that was crashing csound,  
> nothing to do with the python opcodes. These seem to run OK, but I get
> 
> QUTECSOUND: Message buffer overflow. Messages discarded!
> 

I didn't get that message.

--JA

Try it with 'run in terminal' option. If it does what you want, then  
it's QuteCsound.

Victor
On 1 May 2010, at 16:26, Jim Aikin wrote:

>
> Hmm. Sounds like it's a bug in QuteCsound, then.
>
> I don't actually care about the message output. I was just testing  
> to see if
> the Python implementation was working. I'll have to test further to  
> see if
> QuteCsound can handle stuff that I might actually want to do with  
> Python....
>
>
> Victor Lazzarini wrote:
>>
>> Sorry, I was wrong. It was something else that was crashing csound,
>> nothing to do with the python opcodes. These seem to run OK, but I  
>> get
>>
>> QUTECSOUND: Message buffer overflow. Messages discarded!
>>
>
> I didn't get that message.
>
> --JA
>
> -- 
> View this message in context: http://old.nabble.com/Python-in-QuteCsound-tp28419160p28421505.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"

Victor Lazzarini wrote:
> 
> Try it with 'run in terminal' option. If it does what you want, then  
> it's QuteCsound.
> 

Yes, indeed. Running in the terminal shows the Python print statement
outputs. I'll post a message to the QuteCsound list.

--JA

As it turns out, there's a footnote at the bottom of the Csound Journal
article (I didn't notice it initially) confirming that Python print
statements don't show up in the output of front ends. Not a big deal, just
one of those little slippery spots.

--JA