Re: [Pythoncard-devel] Run With Interpreter Broken in OS X?

[Alex T. <al...@tw...>]

Kevin Altis wrote:

>
> On May 13, 2006, at 11:01 AM, Dan Shafer wrote:
>
>> In rummaging about in PythonCard yesterday, I had a need to run an  
>> app with debugging, so I went to the menu option "Run With  
>> Interpreter." Nothing happened. Zip. Zilch. Squat.
>>
>> Running the latest CVS of PC on OS X 10.4.6.
>>
>> Any hints?
>>
>> Dan
>
>
> Depending on how you started the codeEditor or resourceEditor, on the  
> Mac the interpreter prompt should show up in your terminal session or  
> the console. Should be a prompt like >>>. If the application had a  
> syntax error or something like that there would be additional  
> messages. To quit the interpreter type Ctrl-D on the Mac. If you  
> started the codeEditor/resourceEditor using the launcher from your  
> finder desktop then I think any error messages would just show up in  
> the console unless you started with an extra terminal session.

Really ?  Is that what's supposed to happen ? I confess, I had no idea 
.... in fact, I hadn't really noticed that Ctrl+shift+R was described as 
Run with Interpreter.

For me, OS X 10.4 + Pythoncard latest (or nearly latest) from CVS + 
codeEditor + samples/counter.py, what I get is
 - no prompt in the terminal session window
 - typing to the terminal window does nothing
 - application runs OK
 - File / Exit from app - and *then* the prompts, and my typing and any 
responses to it all show up in the terminal window.

Tried on WinXP, and basically the same thing happens (it's set up to 
open a new terminal window rather than use the one from the codeEditor) 
- no prompt visible, print statement output appears in terminal window, 
typing produces no response, until the app exits, and then all prompts, 
typing and output appear.

As I said above - I had no idea that it was supposed to be possible to 
type to an interpreter this way. I have, as far as I can remember, 
always used Ctrl+shift+R  in codeEditor to run the apps, because that 
way the console window remains open, allowing me to examine any output 
until I eventually do my Ctrl+D to close the terminal window. So I've 
never consciously tried typing into that terminal window - but I don't 
recall seeing any ">>>" prompt until the app exits; that's how it's 
been, AFAIK, since I started using Pythoncard about two years ago and 
0.8.1 (or so).

-- 
Alex Tweedly       http://www.tweedly.net



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.5.6/337 - Release Date: 11/05/2006