By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,818 Members | 1,282 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,818 IT Pros & Developers. It's quick & easy.

Naming conventions

P: n/a
Why aren't the names of the modules in the standard library fixed so
that they follow some actual naming convention? That is probably the
biggest deterrent for new users -- having to dig through several
sources to find the module they're interested in. And, as with urllib
and urllib2, it isn't even clear at first glance which is more useful
and when it should be used...

Just curious...I've read a lot about the Python community's collective
determination to maintain the purity of the language and ease-of-use,
and their willingness to fix 'broken' elements rather than gloss over
them in the name of backward compatibility, as Sun often does with
Java :)

Best,

Uzair
Jul 18 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
uz********@yahoo.com (Uzair) writes:
Why aren't the names of the modules in the standard library fixed so
that they follow some actual naming convention? That is probably the
biggest deterrent for new users -- having to dig through several
sources to find the module they're interested in. And, as with urllib
and urllib2, it isn't even clear at first glance which is more useful
and when it should be used...


The usual convention with things like urllib/urllib2 is that someone
writes urllib, people use it and gain experience with it, and learn
that it would benefit from enhancements that would break existing code
that uses it. So a new module gets implemented that has the
enhancements but is incompatible with the old module. That way, new
code can use the new module but old code can keep using the old
module.
Jul 18 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.