Build CLI stuck unless I hit <ENTER> twice

[Mike Williamson]

I needed to use python -m build instead of using PDM like I usually would.

I tried to perform

python -m build

and it just sat there. I changed backends, I went to lunch so that it had plenty of time, etc., and it just sat there.

Then I ran across this issue, which was similar enough to mine that I tried out the suggestion to "Hit enter twice to reveal the command". Not only could I see the command, but then everything worked fine, as long as I hit enter twice. The problem is that I cannot do this in my automated build pipeline.

Some details:

I use fish for the CLI.

> pip --version
pip 23.1.2 from <My Path>/python3.10/site-packages/pip (python 3.10)

> python --version
Python 3.10.6

> fish --version
fish, version 3.6.1

> python -m build --version
build 0.10.0 (<My Path>/python3.10/site-packages/build)

---

Has anyone seen this? What is the fix? Is this already reported (I couldn't see anything).

[Henry Schreiner]

Is that build or pip?

(PS: I'm a fish user and I've never seen it require pressing enter twice)

[Stefan Borer]

Sorry I mixed things up, this is build of course.

IMO this issue is a duplicate, of course the "hit multiple times" workaround is not an actual fix. This is why the linked issue is still open: because it's still not fixed.

[Filipe Laíns]

Do you have any custom pip configuration?