-
Notifications
You must be signed in to change notification settings - Fork 4
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
Release V2.0.0 #69
Release V2.0.0 #69
Conversation
Hi @dlax, I am a little lost by this error. Does this mean I should drop 3.7, limit the version of requests ? https://github.com/dalibo/check_patroni/actions/runs/8617904548/job/23619014594?pr=69#step:6:33
|
I suspect there's something incompatible with mypy being locked to an old version in: Line 26 in e0589b9
and the type definitions of requests, provided by typeshed, that have probably changed since that version. In general, blocking a dependency like that is not a good idea, because, as you can see now, it just shadows issues that would quite likely resurge later on, quite often when you will have little time to handle the original issue and even probably forgotten what the original issue was about... |
So I'd suggest to remove the constraint on mypy version and fix or |
I don't understand why I don't have the same errors on my computer.
|
ra never mind, I scratched my venv en retried (wich I thought I already did). It's the same error now. mybad. |
About the mypy issue; I don't see it with Python 3.11 locally. So maybe you could run that check with python 3.11 in CI (as you do already for tests)? |
ok ... I am just dumb. I didn't see the restriction on the version of mypy in |
No description provided.