Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Version 5.0 drops Django 3.1 support, but can be installed alongside it #90

Closed
tiltier opened this issue Jun 10, 2022 · 0 comments · Fixed by #106
Closed

Version 5.0 drops Django 3.1 support, but can be installed alongside it #90

tiltier opened this issue Jun 10, 2022 · 0 comments · Fixed by #106

Comments

@tiltier
Copy link

tiltier commented Jun 10, 2022

django-timezone-field dropped support for older Django versions, but does not restrict the Django version in its dependency list. Tools like Poetry will conclude that these versions of the library may be installed alongside an unsupported Django version.

The project should make the supported versions explicit, so that automatic upgrades beyond supported versions are averted.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Explicitly depend on django, with correct version range mfogel/django-timezone-field
1 participant
@tiltier