Closed CoolCat467 closed 7 months ago
the failure is from this package not being updated since before trio 0.23, and we having made small changes to the API since. Dirty fix would be to add a requirement for trio==0.xx.yy
- but if we're to release that we really want a warning somewhere that this package is deprecated.
I don't think we can fix this via metadata changes. Pip will just go back in versions and use an earlier version of trio-typing
that is "compatible".
oh right, derp.
Closed in favor of #92 which more properly supports mypy 1.7.
As per #90, this PR makes the project require
mypy < 1.7.0