I saw your comment on GitHub. May be I have to check the consequences of renaming the mount paths on my Mac. Should be the practical solution of the problem.
In summary, the above creates a symlink to your users directory (call it homeward or home or whatever you like), then, instead of storing the virtual environment in .venv in the project directory, sets it in poetry's global config to be in a directory of your choosing. Remove the existing .venv in the project, reinstall the project, and it should use the new virtual environment without spaces.
Hi Jonathan,
I saw your comment on GitHub. May be I have to check the consequences of renaming the mount paths on my Mac. Should be the practical solution of the problem.
What about a symlink?
ln -s /Volumes/Macintosh\ SR0/ /HD
or something similar? I am not a Mac expert; just pondering.The path is already linked:
poetry "sees" the path but ignores the symbolic link.
Michael, what do you think of these steps? Are they a decent, at least temporary, workaround?
You can adapt names, paths, etc to your liking.
In summary, the above creates a symlink to your users directory (call it
homeward
orhome
or whatever you like), then, instead of storing the virtual environment in.venv
in the project directory, sets it in poetry's global config to be in a directory of your choosing. Remove the existing.venv
in the project, reinstall the project, and it should use the new virtual environment without spaces.What do you think?
Hi Jonathan,
thx for your suggestion. The symbolic path exists already:
Create the virtualenv inside the project's root directory leads to:
Using the default virtualenv folder looks much better:
So may be this is the bug in poetry: the shebang line is not the symbolic one if the virtualenv folder is in the project's root directory.
That's well put.