-
-
Notifications
You must be signed in to change notification settings - Fork 422
Suppress "deactivate/activate foo" message #168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Adding something like PYENV_VIRTUALENV_VERBOSE_ACTIVATE would be better. |
Or, use -v argument given to pyenv-virtualenv-init? Both should work at least. From consistency point of view, the former might be better. |
I like quiet pyenv but am worrying about changing default behavior. I want to respect @yyuu 's opinion. |
IIRC, the verbosity in messaging didn't change recently. Or, I didn't intend to change the behaviour at that time, at least. Basically I agree with you; show messages only if there's something wrong should be the default behaviour. Kind of "incompatibility" in behaviour is always a matter and what we should avoid. Although some "changes" in messaging must be allowed. I believe that "quiet by default" principle could be the way for every Unix tools. |
Uh oh!
There was an error while loading. Please reload this page.
I recently installed pyenv-virtualenv and found that entering a directory which I set a local env with
pyenv local foo
makes "deactivate / activate foo" message.I'm used to old behavior - pyenv says nothing without setting VERBOSE - so I feel it's terribly annoying.
I read related Issue #104 #110 and your commit bf7e9ba .
AFAIK prompt changing functionality was restored and can be disabled with setting
PYENV_VIRTUALENV_DISABLE_PROMPT
but activate messages are not. In my opinion providing user a way to disable the message should be provided.Please give me your opinion and if you like it I'll send you a PR. Thanks.
The text was updated successfully, but these errors were encountered: