-
-
Notifications
You must be signed in to change notification settings - Fork 454
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
Update django to 5.0.5 #2131
Update django to 5.0.5 #2131
Conversation
The new |
@@ -393,6 +393,10 @@ django.urls.resolvers.URLPattern.lookup_str | |||
django.urls.resolvers.URLResolver.url_patterns | |||
django.urls.resolvers.URLResolver.urlconf_module | |||
django.utils.connection.BaseConnectionHandler.settings | |||
django.db.models.Q.referenced_base_fields |
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 also have to figure out a way to work with cached_property
without this hack
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 think Django was planning to replace their homegrown cached_property
implementation with functools.cached_property
in 5.1 or 5.2.
If we have the patience to wait until then, this will resolve itself 😄
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 think it might take quite some time? According to this comment and ticket https://code.djangoproject.com/ticket/30949#comment:14
Or is it mentioned to be replaced someplace else?
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.
No, I think you're right, it will take years.
Closes #2130