[ 
https://issues.apache.org/jira/browse/BEAM-11516?focusedWorklogId=657614&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-657614
 ]

ASF GitHub Bot logged work on BEAM-11516:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 29/Sep/21 23:33
            Start Date: 29/Sep/21 23:33
    Worklog Time Spent: 10m 
      Work Description: benWize commented on pull request #15612:
URL: https://github.com/apache/beam/pull/15612#issuecomment-930621611


   Run Python 3.7 PostCommit


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscr...@beam.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 657614)
    Time Spent: 2h 10m  (was: 2h)

> Upgrade to pylint >=2.6.0
> -------------------------
>
>                 Key: BEAM-11516
>                 URL: https://issues.apache.org/jira/browse/BEAM-11516
>             Project: Beam
>          Issue Type: Task
>          Components: sdk-py-core, testing
>            Reporter: Brian Hulette
>            Assignee: Benjamin Gonzalez
>            Priority: P3
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> I accidentally ran the latest pylint (2.6.0 as opposed to 2.4.3 which we 
> currently use), and found that it raised a lot of warnings, many of which 
> looked useful. For example:
> {code}
> apache_beam/pvalue.py:500:11: R1725: Consider using Python 3 style super() 
> without arguments (super-with-arguments)
> apache_beam/utils/timestamp.py:132:6: W0707: Consider explicitly re-raising 
> using the 'from' keyword (raise-missing-from)
> {code}
> We should address these warnings and run 2.6.0 (or whatever is the latest at 
> time of implementation) continuously



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to