Wolf Vollprecht
Wolf Vollprecht
We're playing around with a global "manifest" file that would allow to add multiple packages into a "global env" and also to expose multiple binaries from multiple packages. This configuration...
I am not sure I like either option too much. Wouldn't it be better to let the user figure out how to fix it as part of the build script?
E.g. use a different target_directory for the second download, and then move / copy / rename / delete files in the way they see fit?
Hey @dsherret to be completely transparent the changes here were written by Claude :) I didn't expect you to already take a look tbh. I am trying to fix an...
Here is an explanation in `uv` about the same issue: https://github.com/astral-sh/uv/blob/5f3d46c2413225aac68c86fa24be97c4c2c193e4/crates/uv/src/child.rs#L12-L24 How are you solving this in `deno`? :)
I still need to test in pixi whether this fixes our CTRL+C / kill signal issues. Marked the PR as draft.
Yes, I agree that it could be nice to make a more straight-forward way of building packages from noarch wheels. You should be able to set a wheel as your...
I think we could theoretically try to deduce the import name from the contents of the `sdist` file. But I am not sure whether it's straightforward & worth it.
https://curl.se/libcurl/c/CURLOPT_ACCEPT_ENCODING.html
Yeah this is how tests currently work. We could also think about creating additional `-test` packages automagically with a flag.