From: "Martin Liška" <mliska@suse.cz>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: David Malcolm <dmalcolm@redhat.com>,
gcc-patches@gcc.gnu.org, Gaius Mulley <gaiusmod2@gmail.com>
Subject: Re: [DOCS] Python Language Conventions
Date: Thu, 20 Oct 2022 13:53:30 +0200 [thread overview]
Message-ID: <ff8d5382-f018-8dfd-680e-b1c786d2f40b@suse.cz> (raw)
In-Reply-To: <c7678c6b-d707-e9c9-b5f8-1466ff9b3461@pfeifer.com>
On 10/20/22 13:34, Gerald Pfeifer wrote:
> On Mon, 17 Oct 2022, Martin Liška wrote:
>> All right, let me install my initial patch with the improved wording.
>
> The validator noticed a small issue which I addressed thusly (by
> moving up the </p> - the beginning of <ul> implicitly closes a <p>).
>
> No worries - that's what validators are for. :-)
Heh ;) Thanks for the fix.
Martin
>
> Gerald
>
> commit e9164572d233645b51ed8fa27729a52a0e242984
> Author: Gerald Pfeifer <gerald@pfeifer.com>
> Date: Thu Oct 20 13:04:48 2022 +0200
>
> codingconventions: Fix markup
>
> diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html
> index 9d0a3f14..f88ef019 100644
> --- a/htdocs/codingconventions.html
> +++ b/htdocs/codingconventions.html
> @@ -1486,17 +1486,15 @@ Definitions within the body of a namespace are not indented.
>
> <h2 id="python">Python Language Conventions</h2>
>
> -<p>
> -Python scripts should follow <a href="https://peps.python.org/pep-0008/">PEP 8 – Style Guide for Python Code</a>
> +<p>Python scripts should follow <a href="https://peps.python.org/pep-0008/">PEP 8 – Style Guide for Python Code</a>
> which can be verified by the <a href="flake8.pycqa.org">flake8</a> tool.
> -We recommend using the following <code>flake8</code> plug-ins:
> +We recommend using the following <code>flake8</code> plug-ins:</p>
>
> <ul>
> <li>flake8-builtins</li>
> <li>flake8-import-order</li>
> <li>flake8-quotes</li>
> </ul>
> -</p>
>
> </body>
> </html>
next prev parent reply other threads:[~2022-10-20 11:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 9:37 Martin Liška
2022-10-13 9:44 ` Gerald Pfeifer
2022-10-13 17:16 ` David Malcolm
2022-10-13 20:58 ` Gaius Mulley
2022-10-17 13:06 ` Martin Liška
2022-10-20 11:34 ` Gerald Pfeifer
2022-10-20 11:53 ` Martin Liška [this message]
2022-10-13 10:03 ` Richard Sandiford
2022-10-13 10:16 ` Martin Liška
2022-10-13 14:05 ` Richard Sandiford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff8d5382-f018-8dfd-680e-b1c786d2f40b@suse.cz \
--to=mliska@suse.cz \
--cc=dmalcolm@redhat.com \
--cc=gaiusmod2@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).