Art,

Thanks for your reply, I'm looking forward to seeing it.  I've been talking

with the VPython folks too--apparently it was originally a "pure" python

(plus PyOpenGL, plus Numeric) implementation as well, but was too slow.  Now

it is a mass of C.

I'm curious what in Python is making 3D work so slow even when using

compiled libraries for what should (in my limited understanding) be the

difficult and time-consuming parts.  Are there things that should be added

to Numeric &/or PyOpenGL which would make high-level tools like PyGeo and

VPython doable in "pure" python on top of those libraries?

Because I think 3D is very valuable as a teaching tool, whether you call

it CPFE or PFI (Programming (for the) Fun (of) It), but unless the 3D can

happen in Python (with decent performance) we lose the benefits of using

Python as the teaching language (or at least some of the benefits).

--Dethe

==========================================================================
| Dethe Elza  | delza@[...].org | http://i.am/dethe  | 604-207-4266  |
==========================================================================
"Well I've wrestled with reality for thirty-five years now, doctor, and I'm
  happy to state I've finally won out over it." -- Elwood P. Dowd, Harvey