On Feb 21, 2006, at 12:56 AM, Marko Mikulicic wrote:
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
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.
But as I said the important thing is to code correctly, this are
details.
after doing a perl gig for four years, this was one of the most
refreshing things about python, the flexiblity of its modules, and
that they are refereneceable like any other in-memory object. with
perl everything is hardwired to a totally rigid (and global) package
namespace. if you look around in the standard library, youll find
other examples of module naming games like this to get around issues
that would otherwise need more complicated solutions. I think as
long as you keep namespace games localized and transparent to the
outside world they are a great tool.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users