Henry Schreiner

I've asked here: https://github.com/piccolomo/plotext/issues/214 Looks like it's nearly possible, but the axis wouldn't be great.

`import pkg_resources` should not be broken if setuptools is installed. You have an old version somehow, which probably means setuptools was capped in some package to a version that doesn't...

Ahh, this is getting the surrounding environment. What is your PYTHONPATH set to? Setting that is one way to break pipx, I think.

`'/usr/local/py-utils/venvs/algokit/lib/python3.12/site-packages', '/usr/local/py-utils/shared/lib/python3.10/site-packages'` is a broken sys.path. There's no guarantee any package will work when you have two versions of site-packages for different Python's in your path. Pipx won't add another...

I really don't see where that python3.10 is sneaking in. Everything seems fine in the container, `pyvenv.cfg` looks correct, no `3.10`'s in the environment. Maybe there's an issue using `pyenv`...

Same issue with pdm: ```bash pipx install pdm pdm python install [email protected] pipx install . --force --python /home/codespace/.local/share/pdm/python/[email protected]/bin/python3 pipx-bug-cli ``` Though it's many times faster since these tools (pdm, hatch,...

Also, POSIX has a "C" locale which we should also handle. We can easily fix that, which solves this if the locale is not set to non-English.

#681 should have fixed it. It’s technically a broken environment, so just a patch to help reduce the issue was fine. Will finish up #680 after PyCon.

I linked to the issue in auditwheel. A better variation on this fix would be to check other schemes; this one is `sysconfig.get_path("posix_user", "platlib")`. The core problem is the executable...

It’s building in an isolated environment. You need to add this package to your build-system.requires in pyproject.toml.