Followup to #174. In that PR, we set the lower bound pyarrow >= 14. However, we can't do this because TileDB Cloud still has pyarrow 11 installed.
This PR:
Fixes the conda solver problem by removing the lower bound on pyarrow
In addition it purposefully builds against pyarrow 11. This is a bit overkill since pyarrow doesn't use run exports. However, I wanted to be confident that it could solve an env with pyarrow 11. We could relax this part in the future
Completely skip the Python 3.12 builds. We don't need them now, and it is too much trouble at the moment. Once we relax the above, we can probably add them back
Stopped pyarrrow-hotfix from being installed in the non-cross-compiled build envs
Migrated the recipe to use - {{ stdlib("c") }. I've been meaning to do this for awhile
Followup to #174. In that PR, we set the lower bound
pyarrow >= 14. However, we can't do this because TileDB Cloud still has pyarrow 11 installed.This PR:
- {{ stdlib("c") }. I've been meaning to do this for awhileAll the builds passed on my fork