-
Notifications
You must be signed in to change notification settings - Fork 2k
Avoid warning when environment variables have the same value of OS ones #12128
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
Conversation
|
We require contributors to sign our Contributor License Agreement and we don't have one on file for @dariocurr. In order for us to review and merge your code, please e-sign the Contributor License Agreement PDF. We then need to manually verify your signature. We will ping the bot to refresh the PR status when we have confirmed your signature. |
Done |
|
@conda-bot check |
|
(there's a ton of linter-related changes included in my "fix test failures" commit, which is why the @dariocurr I was going to suggest the updates to |
|
Perfect, thank you. Ready to go? |
|
Thank you so much for this contribution, @dariocurr !! |
|
Thank you @beeankha! It's a pleasure! |
…es (conda#12128) * Avoid warning when env var has same value of os Co-authored-by: Bianca Henderson <bhenderson@anaconda.com>
|
I checked and this hasn't been released yet. We at buildnn would love to use it. When do you plan to release it? |
Description
I believe that the environment variable overwriting WARNING should be printed only if the environment variables are really different from those specified in the OS
Note: another option would be to still send the message, but on
stdoutand not onstderr.I have encountered this behavior dealing with the python extension of vscode, which as soon as has a message on
stderr, forwards it, making itself unusableChecklist - did you ...
newsdirectory (using the template) for the next release's release notes? No since I didn't open an issue and I found in the folder just issue-based news names