-
Notifications
You must be signed in to change notification settings - Fork 45
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
Building from local sources causes two macosx wheels to be produced #1009
Comments
Thanks for testing and the bug report! That is indeed pretty curious. Is your local folder relatively clean (ie. what does Also do things change if you enable the use of |
Ah I should have added: since I cannot easily (at least for now) upstream this into the main The folder was quite clean, nothing but rattler-build and pixi metdata files in it, plus a clone of the numpy repo. I did Creating a git repo in this folder like so doesn't make a difference:
and then adding I'll start over to see if I can come up with a clean reproducer. Perhaps unrelated hiccup found during debugging: I hit Ctrl-C in one run after the wheel was created (because the huge amount of lines that are printed for
With
With
|
Okay, I figured it out - what happened is that I ran This will be a minor annoyance when setting up dev tasks with a local source path, but it's not a caching bug as I initially suspected. I think this issue can be closed @wolfv (unless the panic requires follow-up). |
OK, that's good to hear :) Maybe you can run Regarding the invalid conda file – I'll open a new issue. We should not produce invalid conda files. We should instead create the package in the tmpdir first, and then move it over once done (so that we don't end up with broken packages in the output folder). |
Thanks! Yes, both of those solutions should work. |
I am getting a curious failure when building from a local source path, that I'm not getting when building from an sdist from PyPI with the exact same content. The error happens when building
numpy
on macOS 14 and looks like this:What is happening is that when I build numpy 2.0.1 from PyPI, things works as expected and a conda package rolls out with a
macosx_11_0
wheel as the intermediate binary wheel; with a local git repo checkout of the v2.0.1 tag the build chokes because two wheels appear (amacosx_11_0
one which is expected, and amacosx_14_0
one which is not).Here is the
recipe.yaml
(modified from the example in the docs). It works when uncommenting thesource: - url:
lines and commenting out thesource: path:
lines:And the
build.sh
:Looking at the timestamps of the wheels, the
14_0
old is old:Debugging this is slow, so I thought I'd open a bug report at this point. Questions I have:
MACOSX_DEPLOYMENT_TARGET
environment variable is or isn't set on purpose)?path: ./numpy
doesn't have a distinguishable name that changes when the version changes?The text was updated successfully, but these errors were encountered: