-
Notifications
You must be signed in to change notification settings - Fork 153
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
bdist_wheel should start by cleaning up its build directory #147
Comments
Original comment by Daniel Greenfeld (Bitbucket: pydanny, GitHub: pydanny): Had the same problem at BradWhittington/django-mailgun#28. |
Original comment by Michael Merickel (Bitbucket: mmerickel, GitHub: mmerickel): Same problem here Pylons/pyramid#2525 Used a stale build folder and had no idea that bdist_wheel would ignore setuptools-git. Honestly the best approach would be to just take the sdist and convert to a wheel, since the sdist does what I want. |
Original comment by feluxe (Bitbucket: le0m, GitHub: le0m):
I have the same issue. It's very annoying, because you usually notice the obsolete modules/packages after publishing. So you have to bump version num again, re-build, re-publish, etc... |
Original comment by JonathonReinhart (Bitbucket: JonathonReinhart, GitHub: JonathonReinhart): Do you guys think this issue is the cause of my problem where |
Original comment by JonathonReinhart (Bitbucket: JonathonReinhart, GitHub: JonathonReinhart): I've opened this issue with setuptools (1064) for my problem (which may be related to this one). |
Any news on this issue? I just ran into it nearly 4 years after it was first reported :-( Also are there any workarounds? |
Workaround: remove the build directory before running |
Thanks, I have been investigating the best way to do it. I found this https://github.com/dave-shawley/setupext-janitor, but this seems like overkill. I don't know if this is a good way to do it, but in my setup.py, I have done this:
script_dir_plus_file is defined as follows:
|
Mainly to avoid pypa/wheel#147
Mainly to avoid pypa/wheel#147
If build dir is not cleaned, then building for multiple different Pythons will include extensions compiled for one Python version in the wheels for another version, which conda does not like one bit (among other reasons not to do it): pypa/wheel#147 Add `--no-deps` to pip command. It doesn't seem to be necessary, as I don't see dependencies being installed at build time. However it is recommended so I'm doing it just in case.
Is running |
The name of the issue suggests that |
Related: pypa/setuptools#1871 |
Closing as not relevant to this project anymore as |
Originally reported by: Xavier Fernandez (Bitbucket: xavfernandez, GitHub: xavfernandez)
bdist_wheel does not clean up its build directory making it easy to include obsolete/unwanted files.
On python 2.7, if you run
python setup.py bdist_wheel
once, add a file inbuild/lib.linux-x86_64-2.7
and rerunpython setup.py bdist_wheel
you'll have the file in your wheel.I had this issue with https://github.com/Polyconseil/getconf but it concerns all packages, you can easily reproduce with the wheel package.
It can be quite unsettling, since it bypasses, all MANIFEST or find_packages rules...
It would seem cleaner and safer to simply start from a fresh directory and delete it afterwards.
The text was updated successfully, but these errors were encountered: