Conversation
|
OK, it might be that we have to revert this and talk to the Mypy people. With both 1.20.0 and 1.20.1, the
Does it work for you reliably? cc @Tinche |
That is really weird, yes it works reliably for me, although I did not run it with Edit: Ok I've ran them with |
|
what platform are you on? |
Linux (Fedora). I reckon it's not specific to me and could replicate in a container |
|
I mean I am the one who has a weirdly behaving Mypy. :) And I'm on macOS. |
|
Well, at least in the worst case those test cases can be converted to a regex 🙃 |
|
looks like I "fixed" it by disabling caching on that test #1546 |

Summary
Noticed that the tests were failing locally but not in CI in my recent PR, and turned out it was mypy not working with the latest version. I don't know what the policy is for supporting older mypy so here is a more minimal patch to make it work with the version in the uv.lock. Fwiw, Fedora's tests do not run the mypy tests.
Pull Request Check List
mainbranch..pyi).typing-examples/baseline.pyor, if necessary,typing-examples/mypy.py.attr/__init__.pyi, they've also been re-imported inattrs/__init__.pyi.docs/api.rstby hand.@attr.s()and@attrs.define()have to be added by hand too.versionadded,versionchanged, ordeprecateddirectives.The next version is the second number in the current release + 1.
The first number represents the current year.
So if the current version on PyPI is 26.2.0, the next version is gonna be 26.3.0.
If the next version is the first in the new year, it'll be 27.1.0.
.rstand.mdfiles is written using semantic newlines.changelog.d.