Zanie Blue

Thanks @Tristan971, I believe that one is a manifestation of https://github.com/indygreg/python-build-standalone/issues/374 which we're also tracking in https://github.com/astral-sh/uv/issues/8429 The workaround for this is: ``` export CPPFLAGS="-I/root/.local/share/uv/python/cpython-3.10.16-linux-aarch64-gnu/include/python3.10" export LDFLAGS="-L/root/.local/share/uv/python/cpython-3.10.16-linux-aarch64-gnu/lib" ``` (with the...

I presume the point is that we'd need #9916 for that example to work?

I don't think it's a part of the standard for includes to be present in the virtual environment. See https://peps.python.org/pep-0405/ > The site and sysconfig standard-library modules are modified such...

I'm just following the patterns we're using in our other crates here. I don't have context on why not `etcetera`, cc @charliermarsh. We could change separately from this if we...

Since we're not a GUI application I'm basically down to just move over to XDG entirely too btw.

You could just move it if we find it in the old location? That's what I did when I renamed the Python directory. We could make a link?

Fair, that could be problematic. I guess we "never upgrade" and provide instructions for manual migration?

The lockfile is used for pinning versions: https://docs.astral.sh/uv/concepts/projects/#project-lockfile I think it's almost always an anti-pattern to pin to the latest version in your `pyproject.toml`. Can you share more about why...

I think even with an application, it makes sense to leave the version in the `pyproject.toml` unpinned. There _is_ `--upgrade-package ` which is helpful if you want to only upgrade...

>@zanieb why is it an anti-pattern to pin the version in pyproject.toml? The project metadata is used to declare supported ranges. The lockfile is used to pin to a consistent...