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

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

I've been awefully quiet in this whole discussion, even though I believe it 
was me who's stirred up some waves in trying to get some more Python sanity 
into Visual (sanity as in to behave like every other well behaved Python 
module does).

Reading happily along, and I must say that C Anthony is speaking (writing) out 
*exactly* my feeling/impression. So there's no need to repeat that. (Thanks C 
Anthony!!!)

Anyway, I like the proposal to make "visual" (the module) a convenience module 
that keeps backwards compatibility with the previously large local namespace, 
and make another one the well behaved "cleanroom" module, from which the 
"visual" module then pulls. Along those lines was also a good year (?) back my 
patch that I have provided to pull this off. As Visual (the project) is also 
commonly known as VPython, I think a suitable module name for the clean module 
would be either "vpython" or as also suggested "libvisual". Although the 
latter too much for me connotates with the shared library binary file on UN*X 
like systems.

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