GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||||||||||||||||||||||
GeezerVison is showing github.com — Less strict numpy and pyarrow dependencies by Tom-Newton · Pull Request #74 · databricks/databricks-sql-python Conversation
|
| numpy = [ | ||
| {version = "1.21.1", python = ">=3.7,<3.8"}, | ||
| {version = "1.23.4", python = ">=3.8"} | ||
| {version = ">=1.16.6", python = ">=3.7,<3.8"}, |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
It looks like numpy is barely used in this library so I think pretty much any version should work. I chose >=1.16.6 because that is what the latest version of pyarrow requires.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| {version = "1.21.1", python = ">=3.7,<3.8"}, | ||
| {version = "1.23.4", python = ">=3.8"} | ||
| {version = ">=1.16.6", python = ">=3.7,<3.11"}, | ||
| {version = ">=1.23.4", python = ">=3.11"} |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
It looks like the special requirement for python 3.11 was added recently in #60 so I assume that is important but I changed it to accept >= to this version.
I also think we should only enforce this requirement on python 3.11
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| pandas = "^1.3.0" | ||
| pyarrow = [ | ||
| {version = ">=9.0.0", python = ">=3.7,<3.11"}, | ||
| {version = ">=6.0.0", python = ">=3.7,<3.11"}, |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Probably we could allow even older versions but I think this should make most people happy.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Signed-off-by: Thomas Newton <[email protected]>
Signed-off-by: Thomas Newton <[email protected]>
|
Looks like there is one failure on the CI checks I don't think this can be because of my changes. I guess its just a transient thing but I don't think I can re-trigger it. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Thanks for triggering the checks @susodapop. It looks like all the unittests passed for all the different python versions. One of the code quality checks is failing though. From the error ( If someone could retry that check and review the PR that would be much appreciated. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@susodapop sorry to be impatient but please could you review this? I think this is about to start causing us some significant problems if its not fixed. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Not impatient at all! We just needed to freeze our dependencies to get v2.4.0 out the door. Else this would have merged already. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@Tom-Newton can you grant me push on your fork? I need to re-generate the poetry.lock file before I can merge this but I can't push my version to your fork right now. Also this reminds me that I need to add a segment to our CONTRIBUTING.md file about updating the project dependencies. Unless you regenerate the poetry.lock file then none of the changes are actually picked up during our unit/e2e tests 🤦 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Superseded by #90 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
PyArrow version requirement
There was an error while loading. Please reload this page.