Re: [Visualpython-users] Let's hash out the documentation for restrictive imports

[Guy K. K. <g....@ma...>]

On Sat, 09 Oct 2010 10:41:35 Bruce Sherwood wrote:
> Are you saying that there should be two copies of key components in
> the two folders (which I'll call "visual" and "vpython" for now)? I
> would be nervous about the maintenance issues, although I guess
> installers be built to put copies of files in two places.

No no no. Absolutely not. The code is there only *once*, but as you're 
"mirroring in" parts of the NumPy and math name spaces, you'd be "mirroring 
in" all the stuff into the "visual" package from the "vpython" packages. So 
the "visual" package/module does not really contain any (significant) 
implementations, but just imports/aggregates the stuff from "around the 
house".

> My intention
> is that if the actual implementation is done right it should make no
> difference whatsoever where the components are physically located,
> that importing from the vpython folder will be completely clean,
> independent of where the files are.

Exactly, that's the way I (and probably the others putting up their votes for 
better Python cleanliness) have envisioned it.

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