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
Hi Y'all!
Due to some limitation of where I work, I can only install wheels using pip in production, but it's free to use uv to build wheels.
So when using uv, I want to define a loose range for dependencies for testing, let uv decide the final version for me, but produce a wheel with restrict dependency versions for pip install later. Is there a best practice exists?
Here is a some hypothetical user interface:
uv init --lib proj-for-pip
uv add requests
#got #dependencies = [# "requests>=2.32.3",#]#in pyproject.toml##[[package]]#name = "requests"#version = "2.32.3"#in uv.lock
uv build
# got dist/proj_for_pip-0.1.0-py3-none-any.whl# Requires-Dist: requests>=2.32.3 in metadata of the wheel
uv build --some-parameter-to-lock-version
# got dist/proj_for_pip-0.1.0-py3-none-any.whl# Requires-Dist: requests==2.32.3 in metadata of the wheel
The text was updated successfully, but these errors were encountered:
Hi Y'all!
Due to some limitation of where I work, I can only install wheels using pip in production, but it's free to use uv to build wheels.
So when using uv, I want to define a loose range for dependencies for testing, let uv decide the final version for me, but produce a wheel with restrict dependency versions for pip install later. Is there a best practice exists?
Here is a some hypothetical user interface:
The text was updated successfully, but these errors were encountered: