[python] Revisit numba 0.58 dependency

[johnkerl]

This was updated in #1723 (and release-1.5 branch #1726).

Meanwhile I ran a condability check -- which in hindsight I should have run before accepting #1723 -- at TileDB-Inc/tiledbsoma-feedstock#48.

This failed as noted by @jdblischak at TileDB-Inc/tiledbsoma-feedstock#48 (comment) since numba 0.58.0 is not yet available on conda-forge

numba 0.58.0 isn't available on conda-forge yet

• https://anaconda.org/conda-forge/numba/files
• numba v0.58.0 conda-forge/numba-feedstock#126 open, blocked by
• llvmlite v0.41.0 conda-forge/llvmlite-feedstock#74, which has all-red CI

We may need to revert our dependency back to numba 0.57 until numba 0.58.0 is available at conda-forge.

cc @thetorpedodog @mlin @jdblischak

[jdblischak]

Quick update: Progress is being made (conda-forge/numba-feedstock#126 (comment)), but still no numba 0.58.x available from conda-forge

[jdblischak]

Numba 0.58.1 was merged this morning for conda-forge (conda-forge/numba-feedstock#128, conda-forge/numba-feedstock@172c489)

[johnkerl]

TileDB-Inc/tiledbsoma-feedstock#48 resolves this issue -- the moment we drop support for Python 3.7 (#1790), which is imminent. Leaving this open until then.

[bkmartinjr]

@johnkerl - what (if any) is the action to be taken? Or is this resolved? My understanding is that with the new >=0.58 pin, both conda and pypi backed installs should be fine, as 0.58 is available (in both locations). Closing, but please re-open if I misunderstand the issue.

[johnkerl]

Sorry @bkmartinjr I forgot to signal my intent -- yes, #2122 resolves this, and I wanted to honor/acknowledge your contribution on that front. Thank you!