Re: Style Guide

Am 25.04.15 um 09:52 schrieb Johannes Raggam:
> Currently, I'm also -1 on raising the column length limit. For me, Gil's
> argument weights a lot - I want to be able to make a two column diff and
> see the whole width of both source code documents.
>
> I have no problem with ``# noqa`` and started to use it regulary
> especially for lengthy imports like the following to not break the
> visual flow::
>
> ``from plone.app.contenttypes.testing import
> PLONE_APP_CONTENTTYPES_INTEGRATION_TESTING``
>
> I can remember discussions and random opinions on the 80 column limit,
> but I don't remember a discussion which led to a decision on that topic,
> though.

Sorry, I forgot that this did not make it to the mailing list. After our 
long discussion on the list, we discussed this face to face at the Plone 
conference (I think in Arnhem) and decided to go with 100% PEP8 
compliance. We reached an agreement on the testing team and among the 
p.r.codeanalysis developers.

There has been no "offical" desicion on that topic, because we do not 
have any official coding guidelines. We just have plone.api code 
guidelines and p.r.codeanalysis. Both are the result of long discussions 
within the Plone community. #lesstalkmorecode

Writing a PLIP for coding best practices, officially documenting our 
coding best practices, and running code analysis for Plone core code is 
on our todo list (Gil is already working on the core code analysis).

Timo

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y