OpenERP SA point of view has been posted previously (then /rant extract). About Andrea's comments, you don't have to write in two styles: all you write from now will be CamelCase, but tolerating the other style until all is changed. Also, if you're doing something bad, are you going to do it in this way all your life because you have done it in the past?
Francesco, one example of bug has been showed previously, so there is an strong practical reason to do it. Another not so practical but valid reason is the complete fulfillment of Python coding guidelines (PEP8), which derives in another things out of this scope. Please vote responsibly. Regards. 2014-04-04 16:28 GMT+02:00 Francesco Apruzzese <[email protected]>: > > Il 04/04/2014 16:25, Mariano Ruiz ha scritto: > > I agree with Sylvain, the correct direction is follow the OpenERP SA > guidelines, and if OpenERP SA will be change to CamelCase, then will be > good move to this direction all community addons. > > > It's not important WHAT OpenERP SA guidelines say but WHY OpenERP SA > guidelines say this! > Why change class name in camel case style? Is this usefull for anything? > > _______________________________________________ > Mailing list: https://launchpad.net/~openerp-community > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openerp-community > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
