beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-2000) run pylint on specific module
Date Tue, 18 Apr 2017 17:43:41 GMT


ASF GitHub Bot commented on BEAM-2000:

GitHub user ubunatic opened a pull request:

    [BEAM-2000] run pylint on specific module

    - added module option: any given args to the script will be used as the module for `pep8`
and `pylint`
    - cleaned up bash syntax: removed square brackets, using more explicit `test` command

You can merge this pull request into a Git repository by running:

    $ git pull run-pylint-module-option

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2579
commit 8a3f9a7baedf582790aee90e21ae70897f9715a6
Author: Uwe Jugel <>
Date:   2017-04-18T17:41:15Z

    added module option, use more common zero test, show module name in log


> run pylint on specific module
> -----------------------------
>                 Key: BEAM-2000
>                 URL:
>             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

View raw message