Re: [Visualpython-users] Beta test version of VPython for Python 3.1 for Windows

On Thu, 16 Sep 2010 11:42:30 James Mueller wrote:
>         I have to admit that I am a bit offended by the "physicist make
> happy" comments.  What is being referred to here are in general NOT
> physicists. 

Sorry, no offence intended. But the "physicists" were just the ones commonly 
used here as a representative group of users that are not Computer Scientists.

If this is a feature needed for this or similar groups, then that's fine. It 
would be just a huge shame if the visual package therefore would be spoiled 
for more users with more ambitious Python/programming knowledge.

> Bruce's target audience is College Freshmen, (mainly future
> engineers), who have never taken any programing course.  Bruce wants to
> allow them to investigate their course material visually, and uses the
> python environment to do that.  The concept of namespace is lost on
> them.  I know, as I am teaching some of them right now.  In their
> "computing for freshman engineers" course, they are currently learning
> excel.  Next term they plan to teach them Matlab.  They don't know
> variables; they don't know for or while loops; they don't know physics;
> THEY DON'T KNOW ANYTHING!  So don't call them physicists.

Again, sorry for that, it was just the common nomination previously here.

BTW, I'm an engineer myself (chemical engineer), and the concepts involved are 
not hard to understand. Python is also being taught to engineers at Auckland 
University (one of our PUG members teaches them), and they've got no problems 
to understand. After all, engineers are technical and logically thinking 
people, so they've got what it takes to think in systematic ways.

> Other than that,
> I agree with everything you said.  What I would like to see is something
> like matplotlib where they cleaned up the code but kept the pylab module
> to preserve functionality.  People who know what they are doing, might do
> 
> import numpy as np
> import matplotlib.pyplot as plt
> import scipy
> 
> etc.  but one can also just do
> 
> import pylab
> 
> which ends up importing all sorts of things into the pylab namespace (I am
> not sure how much).  And again most people continue to use it as 
> 
> from pylab import *
> 
> We can cringe, and tell them not to do it, but it was important that the
> option was preserved.  The matplotlib people provide the option but also
> provide ways to do things properly.  I see the same thing in this
> case.  If the code could be rearranged to have proper granularity and
> allow people to use namspaces properly, that would be great!  WE do not
> need to use the "visual" name for that.  Then "visual" can just be
> something that imports everything to reproduce the current visual
> namespace.  We don't need to care as we can use the "correct" imports, as
> long as they exist and are documented.  From Bruce's mail, it seems like
> the option is there to separate the namespaces. whether this is the
> correct separation, I don't know, but seeing all the things visual
> currently loads into one namespace is great.  I can start to use things
> properly.  Most of my students will still "from visual import *", but I
> have something to tell those who do know a little programming.

My biggest issue with the current way visual handles things is, that it 
imports all kinds of non-visual related things from the math and numpy 
packages. And it would get even worse if things imported then are also being 
renamed ("from spam import eggs as seggs").

Namespaces back and forth, certain things just shouldn't be pulled in by a 
base package named visual, that are completely unrelated.

> As always, the devil is in the details, but I think this thread will
> continue.

Yes, indeed. And the issue can only be resolved if it's being discussed.

Only with positive intentions,

Guy

-- 
Guy K. Kloss
Institute of Information and Mathematical Sciences
Te Kura Pūtaiao o Mōhiohio me Pāngarau
Massey University, Albany (North Shore City, Auckland)
473 State Highway 17, Gate 1, Mailroom, Quad B Building
voice: +64 9 414-0800 ext. 9266   fax: +64 9 441-8181
G....@ma... http://www.massey.ac.nz/~gkloss