RetroSearch Browse

Sun Sep 6 02:42:19 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-September/141480.html

On Sat, 5 Sep 2015 at 12:58 Jim J. Jewett <jimjjewett at gmail.com> wrote:

> PEP 498 is only the latest PEP where part of the concern is fear that
> it may encourage certain types of bad code.
>
> Would it be reasonable to ask PEPs to start including a section on any
> recommended changes to PEP8?  (e.g., "If an embedded expression
> doesn't fit on a single line, factor it out to a named variable.")
>
> I realize that there will be times when best practices (or common
> mistakes) aren't obvious in advance, but I'm a bit uncomfortable with
> "PEP 8 will probably grow advice"... if we expect to need such advice,
> then we should probably include it from the start.  (PEP 8 is, after
> all, only advice.)
>

I have no issue suggesting it, but I don't think it needs to be a rule
either.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150906/ba637978/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-September/141480.html below:

[Python-Dev] PEPs and PEP 8 changes