Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-7218

LTS backport: Upper bound for pytz dependency

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 2.7.1
    • Component/s: sdk-py-core
    • Labels:
      None

      Description

      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: yifan zou Is this something dependency notifier can warn on? Dependency without upper version bounds.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                udim Udi Meiri
                Reporter:
                altay Ahmet Altay
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: