On 21.02.2006., at 06:12, Michael Bayer wrote:
> well its Python and I had observed a lot of libraries do have a lot
> of module-level stuff going on....i didnt want to make it too J2EE-
> ish !
of course, nobody wants javish stuff :-), but I always considered
this python "feature" a major problem because it leads to stuff like
import mapper as mapperlib etc
I think you should re-examine your sense of proportion if you condemn a (very useful!) language feature as "a major problem" because you sometimes dislike what people name their modules. :)
and also because sometimes one needs to import using "import
package.module " and then use module.function
and other times "from package.module import Class" ... Class.method,
which imho is less consistent.
I don't understand this objection at all. How is it inconsistent that classes, like anything else, can be individually imported from a module?
--
Jonathan Ellis
http://spyced.blogspot.com
