hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dima Spivak (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18041) Add pylintrc file to HBase
Date Tue, 23 May 2017 22:15:04 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021975#comment-16021975

Dima Spivak commented on HBASE-18041:

Eh, it's probably fine. It's kinda hard to review a big 300 line config file that's full of
commented out stuff since I can't tell what's different from the 'default' and what isn't.
Personally, I'd have started from a clean {{pylintrc}} and then added stuff based on which
errors we think are spurious, but I dunno if it's worth taking the time to go through this
exercise if there's not much value to be gained.

> Add pylintrc file to HBase
> --------------------------
>                 Key: HBASE-18041
>                 URL: https://issues.apache.org/jira/browse/HBASE-18041
>             Project: HBase
>          Issue Type: Improvement
>          Components: community
>            Reporter: Alex Leblang
>            Assignee: Alex Leblang
>         Attachments: HBASE-18041.branch-1.2.001.patch
> Yetus runs all commits with python files through a linter. I think that the HBase community
should add a pylintrc file to actively choose the project's python style instead of just relying
on yetus defaults.
> As an argument for this, the yetus project itself doesn't even use the default python
linter for its own commits.

This message was sent by Atlassian JIRA

View raw message