From: Viet Hung Tran <viethtran1620@gmail.com>
To: Git List <git@vger.kernel.org>
Subject: [GSoC][PATCH 2/2] git-ci: update .pylintrc to ignore current warning
Date: Tue, 13 Mar 2018 23:28:51 -0400 [thread overview]
Message-ID: <20180314032851.11527-2-viethtran1620@gmail.com> (raw)
In-Reply-To: <20180314032851.11527-1-viethtran1620@gmail.com>
pylint's check for unused variables, global statements,
redefined builtins, undefined loop variables, and unused imports are
disabled.
The current configuration allows git-p4.py to pass the check in Travis CI
in my forked repository.
Here is the link for the successful built: https://travis-ci.org/VietHTran/git/builds/353155158
Signed-off-by: Viet Hung Tran <viethtran1620@gmail.com>
---
.pylintrc | 7 -------
1 file changed, 7 deletions(-)
diff --git a/.pylintrc b/.pylintrc
index 0db42d646..09a0019d6 100644
--- a/.pylintrc
+++ b/.pylintrc
@@ -60,20 +60,13 @@ enable=import-error,
used-before-assignment,
cell-var-from-loop,
global-variable-undefined,
- redefined-builtin,
redefine-in-handler,
- unused-import,
unused-wildcard-import,
global-variable-not-assigned,
- undefined-loop-variable,
- global-statement,
global-at-module-level,
bad-open-mode,
redundant-unittest-assert,
boolean-datetime,
- # Has common issues with our style due to
- # https://github.com/PyCQA/pylint/issues/210
- unused-variable
# Things we'd like to enable someday:
# redefined-outer-name (requires a bunch of work to clean up our code first)
--
2.16.2.440.gc6284da
prev parent reply other threads:[~2018-03-14 3:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 2:08 [PATCH] git-ci: use pylint to analyze the git-p4 code Viet Hung Tran
2018-03-12 2:20 ` [GSoC][PATCH] " Viet Hung Tran
2018-03-12 10:15 ` Lars Schneider
2018-03-13 3:36 ` Viet Hung Tran
2018-03-13 14:45 ` Luke Diamand
2018-03-14 0:44 ` Viet Hung Tran
2018-03-14 3:28 ` [GSoC][PATCH 1/2] git-ci: add .pylintrc file Viet Hung Tran
2018-03-14 3:28 ` Viet Hung Tran [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180314032851.11527-2-viethtran1620@gmail.com \
--to=viethtran1620@gmail.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).