visualpython-users

[Visualpython-users] VPython for Python 2.1 on Windows

[Bruce S. <ba...@an...>]

At http://cil.andrew.cmu.edu/projects/visual you can now download VPython 
for Python 2.1 on Windows.

Paul Dubois and Dave Scherer diagnosed the problem we were having with 
Python 2.1, and David Andersen recompiled. Thanks, guys.

The new package no longer overwrites the standard IDLE but creates another 
folder Tools/idle_VPython and shortcuts on the desktop and the start menu 
that point to it. Users also have access to the standard IDLE from the 
start menu.

There is a new demo program, doublependulum.py, which shows chaotic motion 
in a simple system.

The minor source changes to Visual have not yet been checked in to 
sourceforge. They consist essentially of replacing tests such as "a == 
None" with "a is None". Python 2.1 introduced "rich comparisons" to satisfy 
users of Numeric who wanted to do more than test whether one array was 
equal to another. They wanted instead to be able to get an array of true 
and false results for element-by-element comparisons. They also wanted to 
be able to do other comparisons (<, >, etc.). This had a side effect which 
made "a == None" illegal if a is a Numeric array

Bruce Sherwood

Re: [Visualpython-users] VPython for Python 2.1 on Windows

[Dethe E. <de...@al...>]

That's great!  Any ETA for the Mac version?

--Dethe

on 01/6/20 02:55 PM, Bruce Sherwood at ba...@an... wrote:

> At http://cil.andrew.cmu.edu/projects/visual you can now download VPython
> for Python 2.1 on Windows.
> 
> Paul Dubois and Dave Scherer diagnosed the problem we were having with
> Python 2.1, and David Andersen recompiled. Thanks, guys.
> 
> The new package no longer overwrites the standard IDLE but creates another
> folder Tools/idle_VPython and shortcuts on the desktop and the start menu
> that point to it. Users also have access to the standard IDLE from the
> start menu.
> 
> There is a new demo program, doublependulum.py, which shows chaotic motion
> in a simple system.
> 
> The minor source changes to Visual have not yet been checked in to
> sourceforge. They consist essentially of replacing tests such as "a ==
> None" with "a is None". Python 2.1 introduced "rich comparisons" to satisfy
> users of Numeric who wanted to do more than test whether one array was
> equal to another. They wanted instead to be able to get an array of true
> and false results for element-by-element comparisons. They also wanted to
> be able to do other comparisons (<, >, etc.). This had a side effect which
> made "a == None" illegal if a is a Numeric array
> 
> Bruce Sherwood
> 
> 
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> http://lists.sourceforge.net/lists/listinfo/visualpython-users
> 

-- 

Dethe Elza 
Chief Mad Scientist
Burning Tiger Technologies

Re: [Visualpython-users] VPython for Python 2.1 on Windows

[Bruce S. <ba...@an...>]

--On Wednesday, June 20, 2001 15:38 -0700 Dethe Elza <de...@al...> 
wrote:

> That's great!  Any ETA for the Mac version?

David Andersen has VPython partially working on the Mac, but there are 
problems. No estimate possible yet. In going from Python 2.0 to Python 2.1 
on the Mac, there was a change of compilers, which has made the upgrade 
additionally difficult.

Bruce Sherwood

Re: [Visualpython-users] VPython for Python 2.1 on Windows

[Dethe E. <de...@al...>]

>> That's great!  Any ETA for the Mac version?
> 
> David Andersen has VPython partially working on the Mac, but there are
> problems. No estimate possible yet. In going from Python 2.0 to Python 2.1
> on the Mac, there was a change of compilers, which has made the upgrade
> additionally difficult.

That's interesting.  What compilers are you switching to/from?

-- 

Dethe Elza 
Chief Mad Scientist
Burning Tiger Technologies

Re: [Visualpython-users] VPython for Python 2.1 on Windows

[David A. <dm...@an...>]

I'm trying to move from Metrowerks Codewarrior 5.3 with Python 2.0 to 
CodeWarrior 6.2 and Python 2.1.

At the moment, the "label" object isn't working, I'm trying to figure out 
why.