-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Unpin mypy #35667
Comments
This actually seems to be an issue with us pinning django-stubs here: #35275 I think we can move forward with this unpinning, but am not certain enough to do it today. |
Trying this out now that django-stubs and djangorestframework-stubs are unpinned... |
This is possible now that django-stubs and djangorestframework-stubs are unpinned: openedx@a5b773c which became possible once we upgraded to django 4.2. Closes: openedx#35667
Let's see if this passes CI: #36072 |
The above PR hit an internal error with the latest mypy and django-stubs==4.2.1:
The issue was a known bug which was fixed in django-stubs v5.1.1, per python/mypy#17958. So, we'll need to bump django-stubs further forward in order to upgrade mypy. |
mypy was recently upgraded to 1.12.0, and CI ran on that upgrade PR without issue.
Once that PR was merged in with the changes from this collections PR, though, mypy on master started failing with:
The "offending" line does not have anything obviously wrong with it:
edx-platform/openedx/core/djangoapps/content_libraries/api.py
Line 737 in ecbedbc
--show-traceback
adds more details:We are pinning mypy back to 1.11.2 here: #35666
The text was updated successfully, but these errors were encountered: