beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmet Altay (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-2000) run pylint on specific module
Date Tue, 18 Apr 2017 18:00:43 GMT

    [ https://issues.apache.org/jira/browse/BEAM-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973177#comment-15973177
] 

Ahmet Altay commented on BEAM-2000:
-----------------------------------

Makes sense. {{run_pylint.sh}} used to track changed files using {{git}} (see: https://github.com/apache/beam/blob/e1e4b7cef7d0b597cd67fc4039dbf619287b3441/sdks/python/run_pylint.sh).
We removed this because, we wanted the linter the work by default from a source tarball. We
can re-add this functionality behind a flag. Would it be more useful than running against
some selected modules?

> run pylint on specific module
> -----------------------------
>
>                 Key: BEAM-2000
>                 URL: https://issues.apache.org/jira/browse/BEAM-2000
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-py
>            Reporter: Uwe Jugel
>            Assignee: Ahmet Altay
>            Priority: Minor
>
> Since pylint takes quite some time to run on the whole project and since most developers
will touch only a part of the code, the lint script should have an option to define which
module is to be linted.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message