-
-
Notifications
You must be signed in to change notification settings - Fork 463
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
Generic Queryset INTERNALERROR #2479
Comments
I was going to post a similar report. Using Python 3.13 and...
I was updating a
That worked fine until I tried to update the I managed to resolve that error by including a default as per PEP 696 – Type Defaults for Type Parameters, so.
@pelme I wonder, do you still get the error when you include a default for your
Note, you'll need to be using Python 3.13 to set a default, or using the backport by importing I believe #2461 is related too. |
Bisected to 8eeed9b. |
There's a pending error in that library, similar to typeddjango/django-stubs#2479. Unfortunately the upgrade didn't help, developers may have to use `--no-verify` when committing.
There's a pending error in that library, similar to typeddjango/django-stubs#2479. Unfortunately the upgrade didn't help, developers may have to use `--no-verify` when committing.
There's a pending error in that library, similar to typeddjango/django-stubs#2479. Unfortunately the upgrade didn't help, developers may have to use `--no-verify` when committing.
Bug report
Starting from django-stubs 5.0.3, the following example crashes with an internal mypy error:
Output:
How is that should be
Running the same example with django-stubs 5.0.2:
Example project
You can reproduce this by downloading this project (contains the model definition above) and running it locally:
tst.zip
Install django-stubs 5.0.2 without the problem:
Install django-stubs 5.0.3 with the problem
Workaround
The crash can be worked around by putting
TMyBase
after theMyBase
definition.System information
python
version: 3.12.7django
version: I tested with 5.0.4 and 5.1.4 with the same resultThe text was updated successfully, but these errors were encountered: