Describe your idea/feature/enhancement
Update version specification of python-dateutil dependency to allow for version 2.8.1
Proposal
Change the version specification in requirements/base.txt python-dateutil to allow any version compatible with 2.6 (2.6 <= version < 3.0)
# Current
python-dateutil~=2.6, <2.8.1
# Proposed
python-dateutil~=2.6
Additional Details
This is causing unresolvable dependency conflicts in some of our poetry-managed projects. Allowing for all patch versions of 2.8 would solve my particular issue, but it would probably be good to allow up to the next major version.
python-dateutil v2.8.1 was released nearly a year ago (2019-11-03) and appears to only contain bugfixes over 2.8.0
It is unclear why python-dateutil has a specific upper bound on version that is lower than the next major release in the first place. Other dependencies (like PyYAML, click, and Flask) do not have such upper bounds.
Describe your idea/feature/enhancement
Update version specification of
python-dateutildependency to allow for version2.8.1Proposal
Change the version specification in
requirements/base.txtpython-dateutilto allow any version compatible with2.6(2.6 <=version< 3.0)Additional Details
This is causing unresolvable dependency conflicts in some of our
poetry-managed projects. Allowing for all patch versions of2.8would solve my particular issue, but it would probably be good to allow up to the next major version.python-dateutilv2.8.1was released nearly a year ago (2019-11-03) and appears to only contain bugfixes over2.8.0It is unclear why
python-dateutilhas a specific upper bound on version that is lower than the next major release in the first place. Other dependencies (likePyYAML,click, andFlask) do not have such upper bounds.