You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Udi Meiri (JIRA)" <ji...@apache.org> on 2019/06/25 18:09:00 UTC

[jira] [Resolved] (BEAM-7218) LTS backport: Upper bound for pytz dependency

     [ https://issues.apache.org/jira/browse/BEAM-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Udi Meiri resolved BEAM-7218.
-----------------------------
    Resolution: Fixed

> 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: 1h 20m
>  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)