You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/03/09 20:25:00 UTC
[jira] [Work logged] (BEAM-3738) Enable Py3 linting in Jenkins
[ https://issues.apache.org/jira/browse/BEAM-3738?focusedWorklogId=79011&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-79011 ]
ASF GitHub Bot logged work on BEAM-3738:
----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Mar/18 20:24
Start Date: 09/Mar/18 20:24
Worklog Time Spent: 10m
Work Description: holdenk commented on issue #4801: [BEAM-3738] Enable py3 lint
URL: https://github.com/apache/beam/pull/4801#issuecomment-371229849
So @cclauss I don't think that limiting to 3.4.3 is great since someone might read it and then just try to use 3.4.3. Personally I'd use an env variable to (e.g. `LINTING`) and in linting have a different requirement. We also probably want folks to be able to run tox on their own machines since its in the guide.
But I like the direction of selectively unblocking setup.py for testing/linting so that we more easily track our progress and avoid regressions.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 79011)
Time Spent: 2h 40m (was: 2.5h)
> Enable Py3 linting in Jenkins
> -----------------------------
>
> Key: BEAM-3738
> URL: https://issues.apache.org/jira/browse/BEAM-3738
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core, testing
> Reporter: holdenk
> Assignee: Ahmet Altay
> Priority: Major
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> After BEAM-3671 is finished enable linting.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)