[
https://issues.apache.org/jira/browse/BEAM-4606?focusedWorklogId=115519&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-115519
]
ASF GitHub Bot logged work on BEAM-4606:
----------------------------------------
Author: ASF GitHub Bot
Created on: 25/Jun/18 16:59
Start Date: 25/Jun/18 16:59
Worklog Time Spent: 10m
Work Description: udim opened a new pull request #5751: [BEAM-4606] Pin
pytz version
URL: https://github.com/apache/beam/pull/5751
Picked version 2018.4 since it has already pinned in
sdks/python/container/Dockerfile.
**Please** add a meaningful description for your change here
------------------------
Follow this checklist to help us incorporate your contribution quickly and
easily:
- [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA
issue, if applicable. This will automatically link the pull request to the
issue.
- [ ] If this contribution is large, please file an Apache [Individual
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
It will help us expedite review of your Pull Request if you tag someone
(e.g. `@username`) to look at it.
Post-Commit Tests Status (on master branch)
------------------------------------------------------------------------------------------------
Lang | SDK | Apex | Dataflow | Flink | Gearpump | Spark
--- | --- | --- | --- | --- | --- | ---
Go | [](https://builds.apache.org/job/beam_PostCommit_Go_GradleBuild/lastCompletedBuild/)
| --- | --- | --- | --- | ---
Java | [](https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Apex_Gradle/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow_Gradle/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Flink_Gradle/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Gearpump_Gradle/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Spark_Gradle/lastCompletedBuild/)
Python | [](https://builds.apache.org/job/beam_PostCommit_Python_Verify/lastCompletedBuild/)
| --- | [](https://builds.apache.org/job/beam_PostCommit_Py_VR_Dataflow/lastCompletedBuild/)
</br> [](https://builds.apache.org/job/beam_PostCommit_Py_ValCont/lastCompletedBuild/)
| --- | --- | ---
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 115519)
Time Spent: 10m
Remaining Estimate: 0h
> 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
> Time Spent: 10m
> 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)
