Closed rrjjvv closed 1 year ago
Yes, the dependency was added there by mistake, it should have been added in the dev dependencies. I'll merge your PR and cut a new release ASAP.
@rrjjvv thanks for sending a patch 💯
@rrjjvv that's been released in 0.3.1. Thnk you! 🙏
I assume the dependency on mypy was accidental (and possibly a side effect of moving to poetry). Previous to recent updates (before
0.2.0
), the only dependency was oncachetools
(which is expected/reasonable).I only noticed this because I was recreating my environment, where my current mypy (
0.990
) conflicts with your stated dependency constraint of^0.982
. I'm not a poetry user, but my quick reading (and actual error) both indicate that the constraint effectively locks mypy to that specific version (since mypy doesn't utilize 'patch' releases):It would be great if that dependency was removed (or if it's needed for some non-obvious reason, relax the constraint).