-
Notifications
You must be signed in to change notification settings - Fork 16
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
build: Require panda-client
v1.4.82
or later for API stability
#62
Conversation
@kratsg if you can confirm that things are working for you I'll release |
panda-client
1.4.82
or later for API stabilitypanda-client
v1.4.82
or later for API stability
confirmed |
I agree with bumping the required version of the panda client: I have no idea what would work with version 1.0 (probably nothing). Still, give that @kratsg specifically added a workaround so we can use 1.4.81 we should probably say we support it right? Bumping beyond that is telling users / admins that a newer version is required whereas what we want to say is that the older version is deprecated. |
@dguest Given the way that things work, anything in Lines 42 to 43 in d392368
only comes into play if you are But if you are installing from PyPI then it is better to make it clear what are the lower bound of your dependencies and now we have a clear lower bound on using the supported APIs of If we actually want to have a deprecation warning then we should probably raise and then catch a |
Thanks for confirming that we only use That being said, I don't really see a problem with either approach, I'll merge this if that's what you think is best. |
Correct,
I view it as giving the users an assurance: This library is known to safely work with this lower bound of this dependency. This can change in the future as needed, but when you regularly test and update your lower bounds then you know that the releases that people are getting on PyPI will work when in the worst case scenario they or In general trying to support multiple incompatible versions of APIs in your dependencies is a bad place to be as a library and can snowball, especially if your dependencies aren't going to try to follow SemVer in practice or give deprecation warnings in advance. Trying to have releases like |
This PR requires a minimum required version of
panda-client
of1.4.82
for API stability as a follow up PR to PR #58.The backwards compatability that @kratsg added in PR #58
pandamonium/src/pandamonium/panda_kill_taskid.py
Lines 12 to 19 in d392368
should be kept for sometime as at the moment
panda-client
is still older thanv1.4.82
most places.Example on ATLAS Connect:
Squash and merge commit message: