We have discussed this a bit on the pull request and it seems like the main blocker is the “searchability” of the name:
The problem is not what to use for
python -m, but that
buildas a directory name is way too common with established perception.
Personally I would go with a more unique name.
python-buildis also not a very good name since it is the pyenv command to build a Python installation, and I expect most Google results to point there due to pyenv’s popularity.
But since we are opening the scope and bringing more users, I think it should not be that much of an issue, the name would be more widespread as the userbase grows. I think
pip install build is very easy to remember.
If we had a good name to replace it, I would just use it instead, but that is proving difficult. So, I think it is worth to maybe reconsider keeping the name.
We don’t have a clear direction from where to proceed here so things are tricky . I feel myself being pulled from both directions.