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

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

                Author: ASF GitHub Bot
            Created on: 10/Jul/19 22:15
            Start Date: 10/Jul/19 22:15
    Worklog Time Spent: 10m 
      Work Description: kennknowles commented on issue #8917: [BEAM-7218] 
Backport of #7487
URL: https://github.com/apache/beam/pull/8917#issuecomment-510251089
 
 
   It seems that neither `stable` nor `latest` are good choices for the 
pyhamcrest dep. Currently the tip of this branch cannot build docs, I am 
guessing because that version spec has changed.
 
----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


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

    Worklog Id:     (was: 275090)
    Time Spent: 1.5h  (was: 1h 20m)

> LTS backport: Upper bound for pytz dependency
> ---------------------------------------------
>
>                 Key: BEAM-7218
>                 URL: https://issues.apache.org/jira/browse/BEAM-7218
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-py-core
>            Reporter: Ahmet Altay
>            Assignee: Udi Meiri
>            Priority: Major
>             Fix For: 2.7.1
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Do we need an upper bound for the pytz dependency? 
> ([https://github.com/apache/beam/blob/release-2.5.0/sdks/python/setup.py#L108)]
>  We typically have upper bounds, in order to avoid future breakages due to a 
> possibility of breaking/backward incompatible change of that depepdency.
> Good practice is to upper bound either at known version, or next major 
> version. Do we need an exception for pytz because it does not seem to be 
> following semantic versioning?
> cc: [~yifanzou] Is this something dependency notifier can warn on? Dependency 
> without upper version bounds.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to