-
Notifications
You must be signed in to change notification settings - Fork 16
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
[7776] django upgrade to 4.2 (LTS) #1504
Conversation
Coverage reportTotal coverage
Report generated by 🧪jest coverage report action from ec5c807 |
fd5a4f2
to
dbe2d4e
Compare
I'm not entirely sure, but worst case the very few affected users would have to request a new password via |
29c6520
to
1aa189f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@m4ra there are some instances of index_together
which should be replaced with indexes
as described here: https://docs.djangoproject.com/en/4.2/releases/4.2/#index-together-option-is-deprecated-in-favor-of-indexes
28a41d5
to
384f584
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! One thing I missed previously, sorry: (but we can also fix this in a different PR). In tests/project/settings.py
we can now also remove the USE_L10N
option and get rid of the warning.
384f584
to
2c77b8c
Compare
@@ -95,7 +93,7 @@ class Module(models.Model): | |||
|
|||
objects = ModulesQuerySet.as_manager() | |||
|
|||
blueprint_type = BlueprintTypeField( | |||
blueprint_type = models.CharField( | |||
max_length=255, | |||
blank=True, | |||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
then we delete the fields.py with the custom BlueprintType?
Also the new migration cancels the 0008. If we remove 0008, it won't generate 0009 here
@goapunk
8e2b873
to
59fb1f8
Compare
59fb1f8
to
0735f13
Compare
Makefile
Outdated
@@ -45,15 +45,11 @@ lint: | |||
$(VIRTUAL_ENV)/bin/isort --diff -c $(SOURCE_DIRS) || EXIT_STATUS=$$?; \ | |||
$(VIRTUAL_ENV)/bin/flake8 $(SOURCE_DIRS) --exclude migrations,settings || EXIT_STATUS=$$?; \ | |||
npm run lint || EXIT_STATUS=$$?; \ | |||
$(VIRTUAL_ENV)/bin/python manage.py makemigrations --dry-run --check --noinput || EXIT_STATUS=$$?; \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we don't need to remove these anymore, right?
|
||
from adhocracy4.categories import get_category_icon_url | ||
|
||
|
||
class CategoryIconDict(abc.Mapping): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not really sure why this was needed so I removed it, I think we should point out to testers to verify everything still works as intended with the icons
for topic_code in project.topics: | ||
project.m2mtopics.create( | ||
code=topic_code, | ||
name=[item[1] for item in topicsenum if item[0] == topic_code][0], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
topicsenum -> topicenum
90b1927
to
e7313f9
Compare
There was a problem hiding this 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, we only need changelogs for the latest changes (topics, categories?, blueprint_types?) and maybe some of my commits should be squashed
e7313f9
to
ec5c807
Compare
@goapunk done, have another look please. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
really nice!
NOT merge until the other repos are ready
Django 4 has dropped support for sha1 hashes. The deprecation warning was there before Django v3.
From the release notes:
@goapunk will that affect existing passwords? or was it dealt previously while upgrading to 3.2? Cannot find if this is dealt by Django itself.
See transitional notes here, though is about updating multiple instances of same project.
Notes:
DONE: need to update django-allauth for 4.2