Enable flexible channel priority to install tiledb::tiledb-py for py37 #33
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are currently 2 issues that are breaking the linux-64 Python 3.7 nightly builds on the nightly-build branch:
The conda solver is unable to install tiledbsoma-py/libtiledbsoma/tiledb-py/libtiledb in a Python 3.7 environment, so conda is unable to install the run time dependencies for the test section of the recipe. This conda solver error first started back on 2023-06-26. I believe the problem is the strict channel priority, which by default prefers older packages in a higher-priority channel (in this case conda-forge, which only has older tiledb-py available for Python 3.7) over the newer packages available in lower-priority channel (in this case tiledb, because we only build for Python 3.7 in the TileDB-Inc feedstock fork). This PR updates the feedstock to use flexible channel priority, which fixes this problem. Once we no longer need to build for Python 3.7, we should switch back to strict channel priority, since in general this ensures more stable environments
While fixing the above Issue, I discovered that the recently updated
zipp-feedstock
has broken the build step (it's a dependency of setuptools) because zipp dropped support for Python 3.7. This is currently being fixed (zipp 3.16.0 no longer compatible with python 3.7 conda-forge/zipp-feedstock#42, Bump to Python >= 3.8 conda-forge/zipp-feedstock#43), but this PR will fail until the fix is deployed. However, I tested in my fork by temporarily settingzipp <3.16
to confirm that the flexible channel priority fixes the conda solver errorxref: TileDB-Inc/somacore-feedstock#4