Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support building all packages in the workspace including all dependencies #7148

Closed
mmerickel opened this issue Sep 6, 2024 · 1 comment
Closed

Comments

@mmerickel
Copy link

mmerickel commented Sep 6, 2024

I have a workspace like src/*. Now I want to package a subset of those packages and install it into a new virtualenv somewhere.

Backstory example with pip

With pip-tools and uv pip compile I'm starting from a file that looks like this as requirements.in:

-e src/foo
-e src/bar
# ...

And I have a lock file requirements.txt containing:

-e src/foo
-e src/bar
pyramid==1.10.2
# ... all the other remote dependencies

My goal is to end up with a wheel folder containing wheels for foo and bar, as well as everything they depend on. I do it like this:

$ pip wheel -w wheels --find-links wheels -r requirements.txt

Later I can make my new virtualenv and install what I want (let's say just foo) from that wheelhouse via:

$ python -m venv some-env
$ some-env/bin/pip install -w wheels --find-links wheels foo

Adapted version with uv

$ uv export > requirements.txt
$ pip wheel -w wheels --find-links wheels -r requirements.txt

Now I've lost uv's excellent building features and I'm using pip directly instead.

Ideally I'd be able to just say "build wheels including all dependencies", and then I'd say:

$ uv build --wheel -o wheels --with-deps

And it would build foo and everything it depends on including bar, and any external dependencies. And it would use the uv.lock plus the current platform to determine what to build.

@mmerickel
Copy link
Author

I see now this is a duplicate of #1681 which hilariously I even commented on in April so closing this, but maybe the examples are helpful to someone.

@mmerickel mmerickel closed this as not planned Won't fix, can't repro, duplicate, stale Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant