-
Notifications
You must be signed in to change notification settings - Fork 196
fix: restrict python version and update cattrs version restriction #949
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
Conversation
also, lets change the title to something like the following (to fit conventional commit msg standard)
|
Python Tests 8 files + 8 8 suites +8 1m 14s ⏱️ + 1m 14s For more details on these failures, see this check. Results for commit aeb4f61. ± Comparison against base commit ccde3cc. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
3c12965
to
4ff147a
Compare
APIX Tests0 files - 1 0 suites - 79 0s ⏱️ - 3m 15s Results for commit 3120bfb. ± Comparison against base commit fa44a8a. This pull request removes 320 tests.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Just one comment here - pinning python version in a library is a very bad idea. What should people do if they already have python 3.9.10 installed ? This - for example - prevents apache/airflow#20882 from merging. |
The consequence of this change is that any other package that would be released with looker SDK released with this limitation will not be installable not only on Python 3.9.10 but also any other version it follows. This is extremely bad practice to upper-bound a Python version IMHO. I have never, ever seen a library doing it. It might be fine for an application if it has specific requirements and they are broken (because that application might simply be ok to refuse working on specific python version) but restricting an SDK/library to not being installable on a python version means that you are preventing any other packages that use looker SDK in this version from even installing on newer Python versions. |
@potiuk you're correct, it's a less than ideal situation. We're working to resolve the issue but the choice is between pinning it ourselves or letting users find out that it's broken on 3.9.10+ The PR title should have reflected that this is a temporary measure to choose between the lesser of two evils while we find the resources to fix the actual issue |
Description
We need to unpin
cattrs
version to avoid dependency conflicts with other tools using a later version of it.cattrs
version was pinned to1.1.2
due to https://github.com/Tinche/cattrs/issues/119. Since the issue should be fixed incattrs
1.3
, we update the restriction to>=1.3
.Also
python
version need to be restricted to<=3.9.9
due to #944. SincePipfile
doesn't support qualifiers forpython_full_version
, it's set to3.9.9
.