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 Django to 4.2 LTS #184

Merged
merged 1 commit into from
Mar 20, 2024
Merged

Upgrade Django to 4.2 LTS #184

merged 1 commit into from
Mar 20, 2024

Conversation

zubairshakoorarbisoft
Copy link
Contributor

@zubairshakoorarbisoft zubairshakoorarbisoft commented Sep 26, 2023

Description

CheckList

  • Verify Django is upgraded to 4.2 at all places
  • USE_DEPRECATED_PYTZ settings is added to base/common.py with an explanatory comment
  • memcached backend is changed from MemcachedCache to PyMemcacheCache in edx-internal (remote config/ argocd configs)
  • CSRF_TRUSTED_ORIGINS are updated

@UsamaSadiq UsamaSadiq force-pushed the zshkoor/django42-upgrade branch 2 times, most recently from 441a45b to aab3522 Compare October 10, 2023 16:15
@UsamaSadiq UsamaSadiq force-pushed the zshkoor/django42-upgrade branch from aab3522 to f43c397 Compare October 24, 2023 11:07
@iamsobanjaved iamsobanjaved linked an issue Nov 20, 2023 that may be closed by this pull request
@iamsobanjaved iamsobanjaved force-pushed the zshkoor/django42-upgrade branch 2 times, most recently from 8f7efe7 to c65a7e6 Compare November 24, 2023 14:58
@iamsobanjaved iamsobanjaved force-pushed the zshkoor/django42-upgrade branch from 57f20fa to a595593 Compare December 5, 2023 12:36
@iamsobanjaved iamsobanjaved force-pushed the zshkoor/django42-upgrade branch from e00627f to 8ec9277 Compare January 11, 2024 12:13
@iamsobanjaved iamsobanjaved changed the title Open Upgrade Django to 4.2 LTS Upgrade Django to 4.2 LTS Jan 11, 2024
@iamsobanjaved iamsobanjaved force-pushed the zshkoor/django42-upgrade branch from d110337 to 0d4abfe Compare March 6, 2024 17:06
@@ -14,7 +18,7 @@


# using LTS django version
Django<4.0

Copy link
Member

Choose a reason for hiding this comment

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

I believe we should remove the # using LTS django version comment as well.

Makefile Outdated
@@ -108,6 +112,8 @@ upgrade: export CUSTOM_COMPILE_COMMAND=make upgrade
upgrade: piptools $(COMMON_CONSTRAINTS_TXT) ## update the requirements/*.txt files with the latest packages satisfying requirements/*.in
sed 's/django-simple-history==3.0.0//g' requirements/common_constraints.txt > requirements/common_constraints.tmp
mv requirements/common_constraints.tmp requirements/common_constraints.txt
sed 's/Django<4.0//g' requirements/common_constraints.txt > requirements/common_constraints.tmp
mv requirements/common_constraints.tmp requirements/common_constraints.txt
Copy link
Member

Choose a reason for hiding this comment

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

It looks like Django<4.0 has already been removed from common_constraints.txt, and it's now Django<5.0 in edx-lint. Do we need to have this in the Makefile over the long term? Is the risk that the the constraint may be reintroduced?

@iamsobanjaved iamsobanjaved force-pushed the zshkoor/django42-upgrade branch from 0d4abfe to c5d0b6a Compare March 20, 2024 19:27
@iamsobanjaved iamsobanjaved force-pushed the zshkoor/django42-upgrade branch from c5d0b6a to 87c03cd Compare March 20, 2024 19:29
@zacharis278 zacharis278 merged commit 5b45de3 into main Mar 20, 2024
7 checks passed
@zacharis278 zacharis278 deleted the zshkoor/django42-upgrade branch March 20, 2024 20:02
iamsobanjaved added a commit that referenced this pull request Mar 22, 2024
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 edx-exams to Django 4.2
3 participants