in python it is common to see naming inconsistencies ,methods,modules,packages,classes with names in every posible style: thisisalongmethod ThisIsALongMethod thisIsALongMethod this_is_a_long_method and even This_Is_A_Long_Method All over the place,even within one module!
classic static languages dont really need naming conventions, on the other side dynamic languages must have it(in my opinion),since there is a lot of syntax variability and very short constructors, a clear example is what does this means? c = Required(2) is it a method which returns an object or is it a class constructor? this kind of situation greatly decrease readability. whats your opinion on the matter? a) dont care about naming conventions, i use the one i like b) didnt know python has naming conventions,nobody follows them c) naming convention doesnt matters d) i would use one if there was a clear and concise document about python naming style(python style guide is vague) e) i think is very important for readability of source code and easier to use libraries d) other, explain please if you care about it,how could be fixed? if clear conventions were defined,would you change your current naming style? stdlib modules are not going to be touched,but for any new proyect i think python would benefit from an improved,well defined,strict style guide,the one now(http://www.python.org/doc/essays/styleguide.html) is so vague that is not helpfull at all. Ruby for example have a clear naming convention,if python had one,it would benefit greater than ruby,since python source code is much more readable as it is,but it could be better. -- http://mail.python.org/mailman/listinfo/python-list
