Repository navigation
poetry install fails because a space in path to env #3013
Description
-
I am on the latest Poetry version.
I'm on 1.1.0rc1
-
I have searched the issues of this repo and believe that this is not a duplicate.
There are issues that deal with this error but are one or two years old, are closed or marked as fixed and the error output message is different.
-
If an exception occurs when executing a command, I executed it again in debug mode (
-vvvoption).
- OS version and name: Windows 10 v2004
- Poetry version: 1.1.0rc1
- Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/cruzelante098/4a46e9387a50c7ea339adaac5421001f
Issue
poetry install throws the next error:
EnvCommandError
Command "C:\Users\John Smith\AppData\Local\pypoetry\Cache\virtualenvs\dge-bot-KUpJK1g6-py3.7\Scripts\pip.exe" install --no-deps C:\Users\John Smith\AppData\Local\pypoetry\Cache\artifacts\61\a4\b1\1096e79aeb46c7d99c2c17427ce252e25c6bf439f2b2747770cbcda517\zipp-3.2.0-py3-none-any.whl errored with the following return code 1, and output:
ERROR: Invalid requirement: 'C:\\Users\\John'
Hint: It looks like a path. It does exist.
WARNING: You are using pip version 20.2.2; however, version 20.2.3 is available.
You should consider upgrading via the 'C:\Users\John Smith\AppData\Local\pypoetry\Cache\virtualenvs\dge-bot-KUpJK1g6-py3.7\Scripts\python.exe -m pip install --upgrade pip' command.
at c:\users\john smith\appdata\local\programs\python\python37\lib\site-packages\poetry\utils\env.py:944 in _run
940│ output = subprocess.check_output(
941│ cmd, stderr=subprocess.STDOUT, **kwargs
942│ )
943│ except CalledProcessError as e:
→ 944│ raise EnvCommandError(e, input=input_)
945│
946│ return decode(output)
947│
948│ def execute(self, bin, *args, **kwargs):
The error seems to be caused because there's a space in my username, that's included in the path to the virtualenv.
This error has been reported before (#199, #657), but in those instances the error was fixed. This one is happening in the latest version of Poetry.
Activity
abn commentedon Oct 1, 2020
@cruzelante098 can you provided the
-vvvoutput please? Seems that the command itself is being passed intopip.The
ERRORis from pip, not your shell. This is different to #199 and #657.EDIT: realised just after writing this that the issue is that arguments are not quoted.
fcruzel commentedon Oct 1, 2020
@abn here's the
-vvvoutput:-vvvoutputenv/run: ensure all args are quoted as required
fcruzel commentedon Oct 1, 2020
That was quick. Thank you @abn
env/run: ensure all args are quoted as required
env/run: ensure all args are quoted as required
env/run: ensure all args are quoted as required
fcruzel commentedon Oct 1, 2020
@abn the new release (1.1.0) works fine now but there's a new error related to
pyreadline. Thepyproject.tomlremains the same as before, I just moved to a new project to test it and set it to create the env in the project folder:Edit:
I was testing it with Poetry v1.1.0rc1 and found that the error that was fixed in 1.1.0 by #3015 was also caused by the same library,
pyreadline, only that the error message was different:Edit 2:
This issue can be circunvented by installing the package with pip with the virtualenv activated:
poetry run pip install pyreadline poetry install # will continue without issuesabn commentedon Oct 2, 2020
@cruzelante098 does this work in at all?
And when doing
poetry run pip install pyreadlineis it installing fromsdistorexe?fcruzel commentedon Oct 2, 2020
The command throws the same error:
I'd say that is installing it from sdist since
poetry run pip install pyreadline -vvvprint a lot of logs sayingSkipping link: unsupported archive format: .exe; however, I'm not sure at all.fcruzel commentedon Oct 2, 2020
I just realised that
poetry updatefails with the original error because a space in the path:abn commentedon Oct 2, 2020
Looks like poetry is downloading the exe for some reason and pip doesn't like the exe. Can you raise a separate issue for that please? You can work around it by using a url dependency pointing to the zip file directly.
As for poetry update, if you have an older poetrg performing the update you will have the bug since well it is not updated yet. :)
fcruzel commentedon Oct 2, 2020
Oh... I had forgotten that I was using 1.1.0rc1. Thank you.
Sure, I'll open a new issue. Thank you @abn
github-actions commentedon Mar 2, 2024
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.