From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org, Aaron Bauman <bman@gentoo.org>
Subject: Re: [gentoo-portage-dev] [PATCH 4/4] pylintrc: enable more checks
Date: Mon, 3 Aug 2020 18:40:04 -0700 [thread overview]
Message-ID: <d8abb324-dc70-ae5a-c584-2284311f588b@gentoo.org> (raw)
In-Reply-To: <20200804001619.1807070-4-bman@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1781 bytes --]
On 8/3/20 5:16 PM, Aaron Bauman wrote:
> * These checks are already passing... so let's enable them so we do not
> have regressions
> * Sort the checks alphabetically and break into more manageable
> structure
> * Display all warnings/errors from pylint by enabling all messages as
> all listed checks are now passing. This will allow folks to run
> 'pylint' without having to modify the pylintrc.
>
> Signed-off-by: Aaron Bauman <bman@gentoo.org>
> ---
> pylintrc | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/pylintrc b/pylintrc
> index 7fd05f322..1f6867d21 100644
> --- a/pylintrc
> +++ b/pylintrc
> @@ -12,7 +12,15 @@
> # --disable=W".
> #disable=no-absolute-import,bad-continuation,C0103,C0114,C0115,E1101,W0201,no-name-in-module
> disable=all
> -enable=redefined-builtin,useless-object-inheritance,trailing-newlines,unused-import,trailing-whitespace
> +enable=missing-final-newline,
> + mixed-line-endings,
> + redefined-builtin,
> + trailing-newlines,
> + trailing-whitespace,
> + unexpected-line-ending-format,
> + unnecessary-semicolon,
> + useless-object-inheritance,
> + unused-import
>
> # A comma-separated list of package or module names from where C extensions may
> # be loaded. Extensions are loading into the active Python interpreter and may
> @@ -51,7 +59,7 @@ unsafe-load-any-extension=no
>
> # Only show warnings with the listed confidence levels. Leave empty to show
> # all. Valid levels: HIGH, INFERENCE, INFERENCE_FAILURE, UNDEFINED.
> -confidence=HIGH
> +confidence=
>
> [REPORTS]
>
>
Thanks, merged the whole series:
https://gitweb.gentoo.org/proj/portage.git/commit/?id=aa329cafb8f7354a02c4da745ccf9208e0d4e4f8
--
Thanks,
Zac
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
prev parent reply other threads:[~2020-08-04 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 0:16 [gentoo-portage-dev] [PATCH 1/4] lib/portage/output.py: fix unnecessary-semicolon Aaron Bauman
2020-08-04 0:16 ` [gentoo-portage-dev] [PATCH 2/4] lib/portage/emaint/modules/merges/merges.py: " Aaron Bauman
2020-08-04 0:16 ` [gentoo-portage-dev] [PATCH 3/4] lib/portage/util/env_update.py: " Aaron Bauman
2020-08-04 0:16 ` [gentoo-portage-dev] [PATCH 4/4] pylintrc: enable more checks Aaron Bauman
2020-08-04 1:40 ` Zac Medico [this message]
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=d8abb324-dc70-ae5a-c584-2284311f588b@gentoo.org \
--to=zmedico@gentoo.org \
--cc=bman@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
/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