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 3.2 #353

Merged
merged 9 commits into from
Feb 7, 2022
Merged

Upgrade to Django 3.2 #353

merged 9 commits into from
Feb 7, 2022

Conversation

aebruno
Copy link
Member

@aebruno aebruno commented Jan 13, 2022

This closes #295. Upgrade to Django 3.2 along with upgraded all deps.

Notes:

  • Django Q requires setting retry/timeout
  • staticfiles template tag is deprecated. Any custom templates will need to be updated
  • Upgrading will require running coldfront migrate
  • For MariaDB users, STRICT_TRANS_TABLES can be enabled by adjusting the DB_URL config value like so:
DB_URL=mysql://USER:PASS@HOST:3306/coldfront?init_command=SET+sql_mode%3D%27STRICT_TRANS_TABLES%27

mdzik and others added 7 commits August 27, 2021 16:32
name = 'allocation'
name = 'coldfront.core.allocation'

it rises error otherwise
- Set DEFAULT_AUTO_FIELD to maintain the historical behavior and avoid unwanted
migrations. In future Django release the default value will be changed to BigAutoField.

- Set AppConfig.default to False to prevent Django from auto selecting app configuration

- Django Q now requires setting retry/timeout values. It's important that the
timeout value be less that the retry value.
@aebruno aebruno marked this pull request as ready for review January 13, 2022 17:16
@aebruno aebruno requested a review from dsajdak January 13, 2022 17:16
- Ensure plugins use dotted path for app config
Copy link
Contributor

@dsajdak dsajdak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

@aebruno aebruno merged commit d099d6a into master Feb 7, 2022
@aebruno aebruno deleted the upgrade-django-3-2 branch January 29, 2023 03:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade to Django 3.2 LTS
3 participants