Closed tadeu closed 4 months ago
Name | Link |
---|---|
Latest commit | 3a9f3c37643fe14888109cca6e3c19d15057fa10 |
Latest deploy log | https://app.netlify.com/sites/conda-lock/deploys/65a99228aaab3a00082d44d9 |
Deploy Preview | https://deploy-preview-586--conda-lock.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Sorry for not doing this together with the original PR before :blush:
Thanks a lot for the comment, I find it very helpful.
Does this use of stdout_thread
make any functional difference? Like if p.stdout
is true once is it always true?
Does this use of
stdout_thread
make any functional difference? Like ifp.stdout
is true once is it always true?
No functional difference, just maintainability: in case the code is refactored and if p.stdout:
is changed to something different, the other if p.stdout:
would also need to be changed (and it's a bit far away) - now there's no way to change one condition and "forget" to change the other one.
Description
Adding an explanation and a suggested improvement to #581 - it seems important to make it explicit why the thread is there.