bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Cc: Dima Pasechnik <dimpase@cs.ox.ac.uk>
Subject: Re: Python != None
Date: Sun, 25 Feb 2024 12:07:49 -0800	[thread overview]
Message-ID: <f5b6e633-4c34-4686-971d-833f7124d463@gmail.com> (raw)
In-Reply-To: <29ae72cb-550c-44ba-8afc-27f743bc0cda@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 770 bytes --]

On 2/25/24 11:29 AM, Collin Funk wrote:
> I would hope that it just
> involves a simple configuration file that takes the options we have at
> the top of gnulib-tool.py.

Adding the two attached files to the root directory of gnulib should
adjust the warnings to the agreed upon coding style (as far as
pycodestyle and pylint are concerned). It works with Emacs and Eglot
using pylsp. I assume other editors should work similarly.

Not sure if they are worth adding to the repository but I figured I
would share them just incase anyone else wants to work on stuff in the
future.

More information about these files here:
https://pycodestyle.pycqa.org/en/latest/intro.html#configuration
https://pylint.readthedocs.io/en/stable/user_guide/configuration/index.html#

Collin

[-- Attachment #2: setup.cfg --]
[-- Type: text/plain, Size: 156 bytes --]

# setup.cfg

[pycodestyle]
ignore = E265,W503,E241,E711,E712,E201,E202,E221
max-line-length = 136
statistics = True

# Local Variables:
# mode: conf
# End:

[-- Attachment #3: pylintrc --]
[-- Type: text/plain, Size: 163 bytes --]

# pylintrc

[MESSAGES CONTROL]
disable=C0103,C0114,C0121,C0209,C0301,C0302,R0902,R0912,R0913,R0914,R0915,R1705,R1702,R1720

# Local Variables:
# mode: conf
# End:

  reply	other threads:[~2024-02-25 20:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23  5:23 [PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 27 Collin Funk
2024-02-23 13:08 ` Bruno Haible
2024-02-23 22:20   ` Collin Funk
2024-02-23 23:51     ` Bruno Haible
2024-02-24  2:36       ` Collin Funk
2024-02-24  5:49         ` gnulib-tool.py: Follow gnulib-tool changes, part 28 Collin Funk
2024-02-24 23:25           ` gnulib-tool.py: Follow gnulib-tool changes, part 27 Bruno Haible
2024-02-25  0:03             ` Dima Pasechnik
2024-02-25 11:57               ` Python != None Bruno Haible
2024-02-25 19:29                 ` Collin Funk
2024-02-25 20:07                   ` Collin Funk [this message]
2024-02-26 20:38                     ` pycodestyle configuration Bruno Haible
2024-02-26 21:31                       ` Collin Funk
2024-02-26 22:54                         ` Bruno Haible
2024-02-27  0:51                           ` Collin Funk
2024-02-27  2:38                             ` Bruno Haible
2024-02-27  4:22                               ` Collin Funk
2024-02-25 20:55                   ` Python != None Dima Pasechnik
2024-02-25 12:02             ` Python 'strings' Bruno Haible
2024-02-25 19:05               ` Collin Funk
2024-02-24 23:42           ` gnulib-tool.py: Follow gnulib-tool changes, part 28 Bruno Haible
2024-02-25  0:47             ` Collin Funk
2024-02-25  1:18               ` Collin Funk
2024-02-25  1:25                 ` Bruno Haible
2024-02-25  3:32                   ` Collin Funk
2024-02-26 20:51                     ` Bruno Haible
2024-02-28 11:51                       ` Collin Funk
2024-02-28 12:14                         ` Bruno Haible

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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f5b6e633-4c34-4686-971d-833f7124d463@gmail.com \
    --to=collin.funk1@gmail.com \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=dimpase@cs.ox.ac.uk \
    /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).