You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2015/12/04 08:24:11 UTC
[jira] [Comment Edited] (YETUS-218) define project pylintrc file
[ https://issues.apache.org/jira/browse/YETUS-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041194#comment-15041194 ]
Sean Busbey edited comment on YETUS-218 at 12/4/15 7:23 AM:
------------------------------------------------------------
a .pylintrc file in the top level with
{code}
[FORMAT]
# Maximum number of characters on a single line.
max-line-length=100
{code}
and then updating the jenkins job to pass {{\--pylint-options="\--rc-file=$\{COMPONENT}/.pylintrc"}} should do it.
was (Author: busbey):
a .pylintrc file in the top level with
{code}
[FORMAT]
# Maximum number of characters on a single line.
max-line-length=100
{code}
and then updating the jenkins job to pass {{\--pylint-options="\--rc-file=${COMPONENT}/.pylintrc"}} should do it.
> define project pylintrc file
> ----------------------------
>
> Key: YETUS-218
> URL: https://issues.apache.org/jira/browse/YETUS-218
> Project: Yetus
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.1.0
> Reporter: Sean Busbey
>
> we've had a few pylint failures for long lines. the default is 80. anyone opposed to making our project use 100?
> any other pylint checks we should change?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)