You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ofek Using hatch feels a bit cumbersome and lacks some of the concise and elegant features of python, of course, this is just a feeling. So it's just in discussions not issues, a feeling that's not particularly well-described.
@ofek The default virtual environment location should be within the project directory instead of a location in the user directory, especially when it's initially installed. The key point is the default location after installation. The key point is that after installing hatch, the initial default is <project_root>/.venv. This is the effect. Of course, I don’t know how to evaluate it, I just put it forward for discussion.
@ofek I'm sorry, I can only express my feelings, which is a sense of discord with Python's simplicity. Such issues might be better addressed by product design experts. I hope to see more stateless function design in the future, and to manage the scope of the project directory as much as possible from the project's initial state. 😥
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have seen that with hatch one can create virtual environments, but I wonder how does it differ from e.g.
python3 -m venv /path/to/new/virtual/environment
or
conda create --name myenv
Beta Was this translation helpful? Give feedback.
All reactions