dev-requirements.txt: uses mypy==0.790

[blueyed]

While pip install -e . installs "mypy>=0.790" (

django-stubs/setup.py

Line 24 in cc746ab

"mypy>=0.790",

), pip install -r ./dev-requirements.txt installs "mypy==0.790" (

django-stubs/dev-requirements.txt

Line 2 in cc746ab

mypy==0.790

, via 44151c4 (#485)).

dev-requirements.txt is also used on CI, using the pinned/older mypy there for tests: https://github.com/typeddjango/django-stubs/pull/591/checks?check_run_id=2337419461#step:6:124

While I think that pinning (test) dependencies is good in general, I am not sure if this is really intended - and it should probably get upgraded/bumped, or even parametrized on CI maybe?

[sobolevn]

Yes, I guess we can remove mypy from dev-requirements. Because it is specified in setup.py.

[blueyed]

Ok, same for typing-extensions then.

[blueyed]

Started in #593.

What's your take on testing against specific/different mypy versions on CI?

[sobolevn]

What's your take on testing against specific/different mypy versions on CI?

I think that this can be done, but AFAIK, mypy versions are pretty easy to update. And that's what we recommend.
On the other hand, mypy can tweak its internals a bit: sometimes some variables change their "inference" status and start / stop using * in the output. They can also change the type-var numeration. This can be fatal to our tests (blocked by typeddjango/pytest-mypy-plugins#45).

So, it is probably a good thing, but I don't see a lot of value.

[sobolevn]

@bluetech this is a great example of how different mypy versions can fail our CI: #593