You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#25969 mentioned that uv is not available in the python-build-standalone releases (only pip is available). influxdb/main has code for working with uv which is (presumably) broken with python-build-standalone. uv can be installed via pip. As such, either:
the code for uv is removed and influxdb itself only uses pip (easiest; users can choose to pip install uv in the venv if desired)
somehow bootstrap uv as part of setting up the default venv and have influxdb use it instead (not sure of the benefit of this...)
somehow adjust our python standalone build to also ship uv
I suggest '1' for now (especially since we already support influxdb3 install package; I suspect most users won't need to know or care if we are using pip or uv) and see what users want, then exploring 2 or 3.
#25969 mentioned that
uv
is not available in thepython-build-standalone
releases (onlypip
is available).influxdb/main
has code for working withuv
which is (presumably) broken withpython-build-standalone
.uv
can be installed viapip
. As such, either:uv
is removed and influxdb itself only usespip
(easiest; users can choose topip install uv
in the venv if desired)uv
as part of setting up the default venv and have influxdb use it instead (not sure of the benefit of this...)uv
I suggest '1' for now (especially since we already support
influxdb3 install package
; I suspect most users won't need to know or care if we are usingpip
oruv
) and see what users want, then exploring 2 or 3.Tentatively assigning @jacksonrnewhouse, please adjust as needed.
The text was updated successfully, but these errors were encountered: