Re: [Visualpython-users] Experimental clean import capability

[Bruce S. <bas...@nc...>]

Suppose the clean folder is named simply vis? There does not seem to
exist a Python module named vis. It's short, which is nice for those
who prefer to use the full name, as in vis.box(), and by its shortness
it has the flavor of "visual but without the extras imported by
visual". It's similar to your first choice but without the py, which
seems a bit superfluous in the Python environment. And on the other
hand, if someone starts a new project dealing with visualization
they're more likely to call it vispy than vis, because of tradition
(scipy, numpy, etc.).

Whaddya think?

I hope that some people other than me actually try out the machinery I
posted and say whether in fact it satisfies their needs.

Bruce Sherwood

On Mon, Oct 11, 2010 at 8:31 AM, Craig Struble
<cra...@ma...> wrote:
> I don't like visual_parts at all. Too long and is unlike just about every other Python module out there. If vpython is off the table, I'd prefer the names in the order of 1) vispy, 2) visualpy, 3) vislib, 4) visuallib, 5) libvis, 6) libvisual.