public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gaius Mulley <gaiusmod2@gmail.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: "Gerald Pfeifer" <gerald@pfeifer.com>,
	"Martin Liška" <mliska@suse.cz>,
	gcc-patches@gcc.gnu.org
Subject: Re: [DOCS] Python Language Conventions
Date: Thu, 13 Oct 2022 21:58:52 +0100	[thread overview]
Message-ID: <87lepjmodv.fsf@debian> (raw)
In-Reply-To: <d27e3f619542eb78a3657862b97d50274e87a328.camel@redhat.com> (David Malcolm's message of "Thu, 13 Oct 2022 13:16:15 -0400")

David Malcolm <dmalcolm@redhat.com> writes:

> On Thu, 2022-10-13 at 11:44 +0200, Gerald Pfeifer wrote:
>> Hi Martin,
>> 
>> On Thu, 13 Oct 2022, Martin Liška wrote:
>> > I think we should add how Python scripts should be formatted. I
>> > noticed
>> > that while reading the Modula-2 patchset where it follows the C/C++
>> > style
>> > when it comes to Python files.
>> 
>> good initiative, thank you! This makes sense to me, alas I'm not a
>> Python 
>> hacker, so best wait to see what David and Gaius think, too?
>
> I'm very much +1 on recommending PEP 8.

hi,

all sounds very sensible - yes I'm also happy to adopt any house style
and will reformat the code accordingly

regards,
Gaius

  reply	other threads:[~2022-10-13 20:58 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 [this message]
2022-10-17 13:06     ` Martin Liška
2022-10-20 11:34       ` Gerald Pfeifer
2022-10-20 11:53         ` Martin Liška
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=87lepjmodv.fsf@debian \
    --to=gaiusmod2@gmail.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=mliska@suse.cz \
    /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).