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

I'm confused. I thought that what I'd proposed achieves the desired
effect, so I don't understand what the issue is. To repeat:

-----------------------------------------------------------------
Suppose there is in the visual folder a file vobjects.py containing this:

from .primitives import (arrow, cylinder, cone, sphere, box, ring,
     label,  frame, pyramid, ellipsoid, curve ,faces, convex,
     helix, points, text, distant_light, local_light)

Then you could do this:

import visual.vobjects as vo
c = vo.curve(pos=[(0,0,0), (1,0,0), (0,1,0)])

Would this be preferable to the following?

from visual.primitives import curve
c = curve(pos=[(0,0,0), (1,0,0), (0,1,0)])

Similarly, there could be a visual/vector.py file for the vector stuff
(vector, mag, etc.). There are already visual.crayola and
visual.materials files of this kind.
-----------------------------------------------------------

In what way does this not meet expert needs?

Guy, I'm sorry, perhaps I was distracted at the time, but I don't
remember your having made a specific proposal. What I thought had
happened when you first brought this up was that you were studying the
issues. Is your solution very different from mine?

Bruce Sherwood

P.S. There is another import issue I failed to identify, which is that
the text object imports some font- and polygon-handling modules, and
some cleanup may be called for in the submodule file primitives.py.