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.

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

Upgrade to Django 4.0 #8032

Closed
jeremystretch opened this issue Dec 9, 2021 · 1 comment
Closed

Upgrade to Django 4.0 #8032

jeremystretch opened this issue Dec 9, 2021 · 1 comment
Assignees
Labels
status: accepted This issue has been accepted for implementation type: housekeeping Changes to the application which do not directly impact the end user
Milestone

Comments

@jeremystretch
Copy link
Member

Proposed Changes

Move from Django 3.2 to 4.0.

Justification

The most interesting bits from Django 4.0 for us are:

  • Functional unique constraints
  • Built-in Redis cache backend
  • Template-based form rendering

Full release notes are here.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: housekeeping Changes to the application which do not directly impact the end user labels Dec 9, 2021
@jeremystretch jeremystretch added this to the v3.2 milestone Dec 9, 2021
@jeremystretch jeremystretch self-assigned this Jan 11, 2022
@jeremystretch jeremystretch added status: blocked Another issue or external requirement is preventing implementation and removed status: accepted This issue has been accepted for implementation labels Jan 13, 2022
@jeremystretch
Copy link
Member Author

jeremystretch commented Jan 13, 2022

Currently blocked by lack of Django 4.0 support in graphene_django. Relevant PR

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: blocked Another issue or external requirement is preventing implementation labels Feb 1, 2022
jeremystretch added a commit that referenced this issue Feb 7, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: housekeeping Changes to the application which do not directly impact the end user
Projects
None yet
Development

No branches or pull requests

1 participant