-
Notifications
You must be signed in to change notification settings - Fork 157
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
Keep the link when building wheels. #453
Comments
Maybe Line 142 in c05b6b4
|
The wheel spec does not have a specified way to describe symbolic links in |
There's an existing discussion here. Better to contribute there than to open a new topic and split the conversation. |
xref: #203 |
Here is another use case besides shipping shared libraries: support for editable installs when the build system uses out-of-place builds. Out-of-place builds are the only option in Meson, and also good practice for CMake. For out-of-place builds, you ends up with compiled extension modules and generated files in the build directory, and |
There's no point in asking for this here, when the wheel spec itself doesn't even support symlinks. If that is ever added to the spec, a new issue should be created. |
@agronholm I just provided a second use case, which seemed to be missing so far. Guess I'll take it over to the Discourse thread. You may want to close gh-400 as well. |
@rgommers Symlink support in wheels seems to me like a very useful thing to have. But as @agronholm says, it's not currently part of the wheel spec, so it would need a PEP and a new wheel version. You might be interested in this post I just made, and its associated thread, as well as the thread I linked to previously. |
@pfmoore thanks! Our comments just crossed paths, I posted it in the Discourse thread you linked above. I'll keep an eye on both threads. |
Hi there,
I have a dir to pack. And there are some links in it.Like
but when i build wheels, it generated a package that
It lost their links. It cause that the size of package is double than expected.
The text was updated successfully, but these errors were encountered: