Zanie Blue
Zanie Blue
Going to track improving this in https://github.com/astral-sh/uv/issues/8429
I believe `get_config_var("CC")` is always going to return the value CPython was built with. It sounds like 21cmFAST should read the `CC` variable first and prefer that?
I think so! At the very least, it doesn't allow overriding it to your preferred compiler. I'm not sure what downstream best practice is.
Thanks for the report! I'm not sure how best to resolve this; it's going to take some investigation — contributions welcome!
@rsampaths16 I'd be curious to see what happens when that line is removed. I don't remember the implications of it and it seems like there may be difficulty retrieving the...
I think we can track this in https://github.com/astral-sh/uv/issues/6518 I feel relatively strongly that constraints should be defined in the project metadata instead of provided directly to `uv lock`.
This is supported upstream, e.g., https://github.com/axodotdev/cargo-dist/blob/c92b9a1ab36ff8fe0173c80a951a045eed81a760/cargo-dist/src/main.rs#L597-L607
Does `--prereleases disallow` work? The default is `if-necessary-or-explicit` and these are "explicit" specifiers. https://docs.astral.sh/uv/reference/settings/#prerelease
I think that's reasonable too, but low priority to change.
I think we should document this. I'm not sure we should provide a shorthand yet... but it does seem kind of nice?