Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Why does pip wheel -r skip editable requirements? #3291
After reading the documentation, I'm hoping the release process for my project could look like this:
So I'm wondering if the above
My main question being why pip wheel needs to skip editable packages. I found a comment by @qwcode in #1775 hinting at something, but I could not understand the rationale. I my use case (ie releasing a project), it is perfectly desirable to have a wheel generated for editable requirements.
referenced this issue
Dec 13, 2015
Well the point of installing an editable (
You can however
@xavfernandez thanks for looking into this. While I think I understand the point of
Let my explain with a working example. Let's say I'm working on a project called git aggregator.
I first install it with
Then when I'm ready to release to production I freeze with
And then I want to package it for production with
And, bummer, the result is incomplete because pip skips my editable package.
Admitedly I could post-process
Moreover #3379 does work and does not break any test.