Re: [Visualpython-users] Errors running Vpython on OSX

[Steve S. <st...@sp...>]

I worked on sorting this out for a bit (I'm sure all my messages are 
still floating around the numericalpython/python/fink mailing lists.. 
), but I didn't have time to actually figure out what was going on. I 
did find that errno was getting set somehow, but it didn't appear to 
reflect an actual numerical problem, but rather resolved to 'resource 
temporarily unavailable". I'm gussing it's something to do with the way 
idle handles multi-threaded programs, that doesn't work with command 
line python on its own. But.. it's just a guess!

-steve

On Monday, October 7, 2002, at 12:12  PM, Bruce Sherwood wrote:

> I vaguely remember Steve Spicklemire finding an arcane problem with the
> Numeric module on Mac OSX, that was never resolved and which sounds 
> somewhat
> related. Obviously the run environment shouldn't matter. Steve, do you 
> think
> there's some kind of connection here?
>
> Bruce
>
> ----- Original Message -----
> From: "Chris Burns" <bu...@hv...>
> To: "Steve Spicklemire" <st...@sp...>
> Cc: <vis...@li...>
> Sent: Monday, October 07, 2002 11:50 AM
> Subject: Re: [Visualpython-users] Errors running Vpython on OSX
>
>
>> Hi all.
>>
>>> This sounds like the problem I saw when trying to run outside the 
>>> Idle
>>> environment. Are you running inside Idle?
>>
>> Aha!  That's the ticket.  It works fine inside idle.  I actually tried
>> idle the first time, but it turns out I was using the wrong one.  
>> Python
>> comes with it's own idle in /sw/bin (which was first in the path, 
>> before
>> /usr/local/bin/idle).  Thanks!  Now I can show my students all the 
>> nifty
>> things we can do.
>>
>> So what's so special about the idle environment?  I thought it was 
>> just
>> window dressing for the python interpreter.  I'm a command-line
>> enthusiast (and I edit my programs in vi), so I prefer just running 
>> from
>> the shell, which works fine in Linux.  Just curious why OS X is so
>> different.
>>
>> Chris
>