Create subsets of pyarrow package with pyarrow-core < pyarrow < pyarrow-all and update to Arrow v16.0.0#1376
Conversation
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
b8e17a8 to
b39a6f3
Compare
|
Hi! This is the friendly automated conda-forge-linting service. I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug. |
b39a6f3 to
1443361
Compare
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
1443361 to
a632f02
Compare
I can revert those but I am not sure what you mean by |
…ividual dependencies
ce176b3 to
99dbba1
Compare
|
This PR is now ready from my side. However, unless there's very concrete urgency, I'd like to wait a couple of days until people have had a chance to respond to #1381, which would simply entail moving all the |
|
Ah actually, something is still amiss. We're not creating different hashes between the CUDA & non-CUDA python wrappers. That wouldn't be an issue per se (especially if we do #1381), but it is an issue since we're currently doing
|
|
Ugh, the move from CUDA 11.2 -> 11.8 seems to have caused the aarch builds to hang (CC @jakirkham), and the non-CUDA build on ppc is now crashing in the test suite. No idea if this could be related to pytest 8 somehow, the stacktrace is useless. |
I don't think it is as in my last commit (removing the pytest pin) ppc was successful, there was only a flaky test failure on aarch64 |
Are you sure? Because 99dbba1 came after your last commit. |
True, I forgot that I didn't push the revert even though I did it locally. I've done so many tests and changes on this PR that I should give it some time :) |
…nda-forge-pinning 2024.05.02.11.25.06
|
Turns out it's related to the compiler version. Both GCC 11 (newly pulled in because CUDA 11.8 allows it) breaks on linux-aarch64 and GCC 12 leads to problems on ppc (like it did on aarch). |
h-vetinari
left a comment
There was a problem hiding this comment.
OK, this is ready for merging now. I'd still like to hear some feedback on #1381, but if we cannot come to a decision there quickly, I'm OK to merge this as-is and deal with the split later.
…nda-forge-pinning 2024.05.06.20.57.12
…ackage split (#41135) Do not merge until some discussion is had about how to time this relative to conda-forge/arrow-cpp-feedstock#1376. Additionally, consider hot-patching this into arrow-site if appropriate. ### What changes are included in this PR? Updates to the [Python installation docs](https://arrow.apache.org/docs/python/install.html) to reflect the in-progress change splitting PyArrow on conda-forge into three separate packages. Specifically: 1. Add a note in the conda section highlighting that there are three packages and linking to a new section (2) in order to provide more information 2. Add a new section, linked from (1), providing a comparison of each package as a table ### Are these changes tested? These are just docs changes. I have built them locally and they look fine. ### Are there any user-facing changes? Just docs. * GitHub Issue: #41105 Lead-authored-by: Bryce Mecum <petridish@gmail.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Signed-off-by: Bryce Mecum <petridish@gmail.com>
…onda package split (apache#41135) Do not merge until some discussion is had about how to time this relative to conda-forge/arrow-cpp-feedstock#1376. Additionally, consider hot-patching this into arrow-site if appropriate. ### What changes are included in this PR? Updates to the [Python installation docs](https://arrow.apache.org/docs/python/install.html) to reflect the in-progress change splitting PyArrow on conda-forge into three separate packages. Specifically: 1. Add a note in the conda section highlighting that there are three packages and linking to a new section (2) in order to provide more information 2. Add a new section, linked from (1), providing a comparison of each package as a table ### Are these changes tested? These are just docs changes. I have built them locally and they look fine. ### Are there any user-facing changes? Just docs. * GitHub Issue: apache#41105 Lead-authored-by: Bryce Mecum <petridish@gmail.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Signed-off-by: Bryce Mecum <petridish@gmail.com>
Checklist
0(if the version changed)conda-smithy(Use the phrase@conda-forge-admin, please rerenderin a comment in this PR for automated rerendering)Continuation of #1255