On 19 January 2016 at 20:12, Brett Cannon <br...@python.org> wrote:
> Here is a proposed update:
>
> diff -r 633f51d10a67 pep-0007.txt
> --- a/pep-0007.txt Mon Jan 18 10:52:57 2016 -0800
> +++ b/pep-0007.txt Tue Jan 19 12:11:44 2016 -0800
> @@ -75,9 +75,9 @@
> }
>
> * Code structure: one space between keywords like ``if``, ``for`` and
> - the following left paren; no spaces inside the paren; braces may be
> - omitted where C permits but when present, they should be formatted
> - as shown::
> + the following left paren; no spaces inside the paren; braces are
> + strongly preferred but may be omitted where C permits, and they
> + should be formatted as shown::
>
> if (mro != NULL) {
> ...
This change seems to be accidentally smuggled in, in the guise of a
PEP 512 update :)
My view is I prefer always using curly brackets in my own code. It is
easier to add printf() debugging without making mistakes. I support
“strongly preferring” them in the style guide, which is as much as a
style guide can do anyway.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
