[
https://issues.apache.org/jira/browse/BEAM-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518777#comment-16518777
]
Ahmet Altay commented on BEAM-4606:
-----------------------------------
Let's do something like >=2018.3,<=2018.4. if we use ==2018.3 we will break
users who have 2018.4 in their environments already. (This is the case for
dataflow worker containers.)
> Upper bound for pytz dependency
> -------------------------------
>
> Key: BEAM-4606
> URL: https://issues.apache.org/jira/browse/BEAM-4606
> Project: Beam
> Issue Type: Improvement
> Components: sdk-py-core
> Reporter: Ahmet Altay
> Assignee: Udi Meiri
> Priority: Major
>
> 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)
