venvs are stored in /Users/x/Library/Application Support - space is not supported about hatch HOT 9 CLOSED

I think it will be good to use ~/.virtualenvs in Mac. Because pipenv is also using that directory.

from hatch.

Thanks! Could you please tell me what directories are located in your virtual env bla?

from hatch.

@chbndrhnns Can you paste more of your terminal session?

from hatch.

I found:

https://stackoverflow.com/a/36236806/5854007
https://stackoverflow.com/a/45534625/5854007

from hatch.

@chbndrhnns I did a bit more digging and discovered https://github.com/kennethreitz/pipenv/issues/234

So it seems this is not a bug in Hatch, but rather virtualenvwrapper simply doesn't play nicely with other venv managers.

I'll leave this open for today though. Please let me know what you end up doing!

from hatch.

Following https://stackoverflow.com/a/36236806/5854007 worked well. Thanks very much!

from hatch.

I'm glad that helped, enjoy!

from hatch.

I'm encountering the same issue in Mac OSX. I am using Python 3.6. But I can not fix it with the link you provided.
My problem is hatch can generate virtual env. But when I hatch use. Nothing happens. After I source path/to/active manually it works. But when I run pip an error happens. bad interpreter: "/Users/chenbojian/Library/Application: no such file or directory
I tested by myself and find that in the pip file, the shebang line is #!"/Users/chenbojian/Library/Application Support/hatch/venvs/test/bin/python3" .
So it looks like that shebang can not support executable in a directory with space. I think this is not a hatch issue. However, can we be able to customize VENV_DIR in hatch instead of always using user_data_dir.

from hatch.

@chenbojian I think instead I'm going to make a breaking change and use ~/.virtualenvs like other tools do. What do you think?

from hatch.