Replacing Pyenv?

[hydrosquall]

Hi,

I noticed that the project says that it replaces a whole multitude of tools, including pyenv.

Does this indicate that you'd recommend using this as the sole python package in the global python package space? Or could hatch be safely used from within a virtualenv that was produced by pyenv? (I'm not sure if hatch modifies $PATH or any other environment variables from quickly browsing the project).

[ofek]

Hatch doesn't replace all the functionality of all those tools, just the core/most common use cases. :)

You may certainly safely use Hatch from an env activated by other means. Hatch only modifies $PATH when it activates an env i.e. hatch use .... Also, please note when you do this that only the subprocessed shell's environment is altered, not yours.

[hydrosquall]

Thank you for clarifying! Will give this a go inside one of my pyenv virtualenvs sometime soon then.

[ofek]

Please let me know how you like it!