-
Notifications
You must be signed in to change notification settings - Fork 648
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 pip wheel
subcommand
#1681
Comments
We have all the plumbing to do this, I'm not sure where it fits on our roadmap though. I'm curious how this would relate to |
Pip would prefer to remove the
|
Thanks for the additional context. I wonder what we can provide for people who want to generate wheels for all their dependencies though. It makes sense for pre-building and sharing when they aren't distributed by the original package. |
I echo this. |
But it doesn’t actually put wheels in the wheelhouse if there’s already a built wheel, IIRC? Pip download will get everything you need then you can loop over any SDists and build them if you need them? |
@henryiii I'm not entirely sure what you mean with that?
Sure. Actually |
That said, |
That's the problem, it does not store wheels that are downloaded. So if you depend on |
That's strange. It is not my understanding of how Now if the purpose is uploading wheels to an index, I'd use |
I’ll investigate, maybe it changed or there’s an another reason it was behaving like that. |
I'd like an
|
Small comment on that one (I do not contest the need for pip wheel of course just explaining how we are doing it in Airflow). I found that you can do quite a bit better than that by just copying the whole Smthing like:
That saves the hassle of running |
Just to second this issue, my pipeline is dependent on the recursive nature of |
I tend to think of
The default is not the most common operation during development, and the functional behaviour provided by None the less, my two cents would be that this shim should not be provided and uv should instead focus on its own dedicated CLI outside of the pip namespace; keeping these two "consumer" and "publisher" pieces separated. |
To second this issue, In our usecase we build the wheel once ( |
FWIW I added a concrete example of how I use pip wheel to #7148 if it's helpful in motivating this feature. |
The command |
The issue is that the new command doesn’t build the dependencies. Neither the local dependencies in the workspace nor the remote dependencies from the package index. |
This would be useful for packaging Blender extensions, which need their dependencies bundled as wheels in a subdirectory: https://docs.blender.org/manual/en/dev/advanced/extensions/python_wheels.html |
This issue is essential to adopt |
I've been trying
uv
on work projects to assess its coverage and suitability of being a fullpip
/pip-tools
replacement for us. One of the features of pip that we use ispip wheel
, which seems to not be supported byuv
currently and I couln't find an open ticket discussing it, so I'm making one here.The text was updated successfully, but these errors were encountered: