-
Notifications
You must be signed in to change notification settings - Fork 121
Do not move stuff around in setup.py #88
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
Conversation
|
Should the dlls be part of the |
|
Yes, they should be. Otherwise you will not be able to build it from PyPI. I have done something similar recently and will check what I did to fix it. |
|
Regarding |
|
OK, I have implemented a solution that packages the DLLs in the sdist ZIP file. However I cannot test if Windows will be able to find the files in their new location. Can anybody check? |
|
Thank you for your contributions. Any simplification of the binary DLL handling is greatly appreciated. At the time, I merely went with the thing that worked, which is probably not the most elegant solution. However, I wouldn't want to copy all binaries into all bdist packages. Also, I don't think that we need to convert PySoundFile into a package. I like the fact that you can just |
I would go with whatever makes PIP installs more easy. I couldn't find a way to having a module and having |
|
Oh, I see. |
|
We'll try to get rid of the binaries altogether. We'll reevaluate this question once that process is done. |
|
I created an alternative to this PR: #98. |
|
I'm closing this, see #98 for the reasoning. |
Your current approach of moving stuff around in
setup.pyis very unclean:Even without passing an actual action (
install,sdistetc.) the script will copy stuff around. Also, you will not be able to build source packages for Windows when you are on any other operating system.My solution: Always ship the DLLs and make the distinction in your actual module, not in
setup.py.