Zanie Blue
Zanie Blue
What is gained by switching from "Initialized project" to "Initialized application" and "Initialized library"?
I believe this may be the problem in https://github.com/indygreg/python-build-standalone/issues/376 as well, but haven't been able to produce a fix yet to confirm.
Ah this is a bit annoying because now we're locking the directory before we make sure it exists, which I preferred to have happen once we knew we wanted to...
@charliermarsh you can see the CI failures are due to the lock being acquired without `init` first which throws an error. Previously, we waited to call `init` until we needed...
Huh, this passed locally but fails here. Need to dig deeper, I guess.
Per https://github.com/astral-sh/uv/issues/7275 we're just matching the behavior of the `python` binary which supports `python ./dir` to execute `python ./dir/__main__.py`? (that's what motivated https://github.com/astral-sh/uv/pull/7281 adding the behavior)
I can see why (3) would be preferable, but breaking from the convention of the `python` binary will require a strong justification and I disagree that we've chosen "the worst...
These were last published in https://github.com/astral-sh/python-build-standalone/releases/tag/20230826 (under the i686 name) and removed in https://github.com/astral-sh/python-build-standalone/releases/tag/20231002 due to lack of downloads.
Related https://github.com/astral-sh/python-build-standalone/issues/50
Thanks for following up! I wonder if there's a place for this in https://docs.astral.sh/uv/reference/build_failures/