layday

I don't have Spack, but here's a simple repro using Nix, which manipulates the Python path in the same way: ``` $ nix-shell -p python39.pkgs.pip --command fish $ python -m...

Ultimately, this needs to be fixed in Python. If `ensurepip` should ignore entries on the `PYTHONPATH`, the environ needs to be manipulated in [venv](https://github.com/python/cpython/blob/f1bcdeaca6e912a2bec1fbcff76cc49e7f761d38/Lib/venv/__init__.py#L335-L336). Invoking Python with `-I` is not...

In build, it will be mitigated by #406 (https://github.com/pypa/build/pull/406/commits/38099ad07636311d5ca8e810baf12b952b8f2568), should it be merged at some point.

Okay, I had assumed there was some interplay with installing pip with Python, but it makes things a lot easier if there isn't.

Can't flit_core and tomli just run `prepare_metadata_for_build_wheel` whenever they bump their version number and store the metadata folder in the repo, next to the package? Installing either one of them...

> Doesn't seem like a great option since it's kinda noisy in the commit history. It's no more noisy than bumping the version. > That means custom handling for each...

I think you're misunderstanding - I don't want to parse the wheel filename into its constituent tags. I want `build` simply to return the filename of the distribution file the...

Perhaps this is something that we could roll into #192 - if the output format were to be customisable - say, if `build` could grow a provisional `--output-format=(human|json)` option, and...

Thanks for the detailed report! This is (sort of) tracked in #373 and will be fixed by #361.

Are you seeing the same error or a different error?