-
-
Notifications
You must be signed in to change notification settings - Fork 557
Type admin site as DefaultAdminSite inheriting from Adminsite #3296
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
Open
ahmedasar00
wants to merge
1
commit into
typeddjango:master
Choose a base branch
from
ahmedasar00:fix/default-admin-site
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+3
−4
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
This one is tricky but I don't think this is a correct fix.
The LazyObject make this
sitebehaves like anAdminSiteobject. You can try it yourselfThere 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.
Thanks for the review! I agree it's tricky, I understand that
DefaultAdminSiteproxies toDefaultAdminSiteviaLazyObject, not through actual inheritance.!What would be the correct approach here?
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.
What is the stubtest error exactly ?
We probably will just have to mive this allowlist entry to the main allowlist.txt with a comment, possibly next to similar entries if there are any
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.
error:
django.contrib.admin.sitevariable differs from runtime typedjango.contrib.admin.sites.DefaultAdminSiteStub: in file
django-stubs/contrib/admin/__init__.pyi:86django.contrib.admin.sites.AdminSiteRuntime:
AdminSite(name='admin')And the same for
django.contrib.gis.admin.site.I can update this PR to move the entry to
allowlist.txtwith a comment instead, if you'd prefer that approach.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.
My preference would be to get to the bottom of this, it's either a bug in stubtest or something wrong with how we type LazyFunc or use it here
Should it be that maybe ?
but
site: DefaultAdminSitewill cause false positives for pretty much every attribute access that are expected on AdminSite but not present here no ?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.
Interesting finding:
type(site)returnsDefaultAdminSite, butsite.__class__returnsAdminSitebecauseLazyObject.__getattr__proxies__class__to the wrapped object. That's whyisinstance(site, AdminSite)isTrueeven thoughissubclass(DefaultAdminSite, AdminSite)isFalse.So the issue seems to be that stubtest uses
type(site)and seesDefaultAdminSite, while the stub saysAdminSite. This might be a stubtest limitation, it doesn't account forLazyObject's__class__proxying behavior.Should I investigate how
LazyObjectis typed to see if there's a way to make this work properly?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.
@sobolevn Shoul we do something about it ? Is it a stubtest limitation with thes proxy objects ?