openerp-community team mailing list archive
-
openerp-community team
-
Mailing list archive
-
Message #04055
Re: Coding Guidlines - long lines
Hello Raphael I also understand the question why the question was rised,
also, I do not think that PEP8 Is ambiguous, it says maximum of 100 with
effective 99 for code mantained by a team, so, we, as a team, are allowed
to a maximum of 100.
Regards.
On Fri, Nov 22, 2013 at 10:04 AM, Raphael Valyi <rvalyi@xxxxxxxxx> wrote:
> On Fri, Nov 22, 2013 at 1:52 PM, Oscar Alca <oszckar@xxxxxxxxx> wrote:
>
>> I don't think that there is a reason to have this discussion, PEP's were
>> made by a reason indeed, and PEP8 is known by allmost all Python
>> programmers, so here is the scenario, imagine that in a month from now a
>> old Python programmer dives into the OpenERP world, is he going to read all
>> historic data on the mailing lists to catch up with all the things that we
>> discussed and established?, even if we agree to do it one way or another,
>> will OpenERP SA publish this on the docs as a guideline?, Python has its
>> own best practices (known and available to everybody) and OpenERP too,
>> please do not try to reinvent the wheel.
>>
>> BTW, I do not want to be rude, it's just my humble opinion.
>>
>> Regards.
>>
>
>
> Oscar, again there is this discussion exactly because this is a thing that
> became ambiguous in PEP8: was originally 80 chars and now states:
> "Some teams strongly prefer a longer line length. For code maintained
> exclusively or primarily by a team that can reach agreement on this issue,
> it is okay to increase the nominal line length from 80 to 100 characters
> (effectively increasing the maximum length to 99 characters), provided that
> comments and docstrings are still wrapped at 72 characters."
> http://www.python.org/dev/peps/pep-0008/
>
> I personally have no strong opinion about the choice, but let's say I
> understand why the question was raised.
>
>
> Regards.
>
>
> --
> Raphaël Valyi
> Founder and consultant
> http://twitter.com/rvalyi <http://twitter.com/#!/rvalyi>
> +55 21 2516 2954
> www.akretion.com
>
>
>
--
Ing. Oscar Alcalá Rivera
*312-107-1704* · oszckar@xxxxxxxxx <ozckar@xxxxxxxxx>
Paseo de Bugambilias 251 · Villa de alvarez, Colima, CP 28978
Tlf: *3123111122*
*Open Source Enthusiast*
[image: twitter] <http://twitter.com/oscarolar> [image:
linkedIn]<http://www.linkedin.com/pub/oscar-alcal%C3%A1/3b/a79/922>
[image: Google+] <http://plus.google.com/107659954580035981067/posts>
[image: eco] No me imprimas si no es necesario. Protejamos el medio ambiente
Follow ups
References
-
Coding Guidlines - long lines
From: Markus Schneider, 2013-11-15
-
Re: Coding Guidlines - long lines
From: Grahame Jordan, 2013-11-21
-
Re: Coding Guidlines - long lines
From: Alexandre Fayolle, 2013-11-22
-
Re: Coding Guidlines - long lines
From: Nhomar Hernández, 2013-11-22
-
Re: Coding Guidlines - long lines
From: Alexandre Fayolle, 2013-11-22
-
Re: Coding Guidlines - long lines
From: Niels Huylebroeck, 2013-11-22
-
Re: Coding Guidlines - long lines
From: Lionel Sausin, 2013-11-22
-
Re: Coding Guidlines - long lines
From: Raphael Valyi, 2013-11-22
-
Re: Coding Guidlines - long lines
From: Raphael Valyi, 2013-11-22
-
Re: Coding Guidlines - long lines
From: Oscar Alca, 2013-11-22
-
Re: Coding Guidlines - long lines
From: Raphael Valyi, 2013-11-22