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
Do not document buggy behavior. #49325
Do not document buggy behavior. #49325
Conversation
Note that the umask should be specified as an octal *string*, not an octal (or decimal) *integer*. +label: docsite_pr
Hi @pillarsdotnet, thank you for submitting this pull-request! |
I don't agree with removing this, as long as people could be writing it as an integer they might end up with unexpected results and the documentation now lacks information. Maybe the wording could be better, and maybe it should be a note, rather than part of the parameter description, but we do need to warn/inform users about this. Pretending there is no issue when there is, is worse from a support perspective. cc: @abadger |
@pillarsdotnet @abadger I implemented my proposal above. I introduced a newer type You can find the PR here: #50035 Also, this PR cleans up a lot of examples doing it wrong. |
In the pip module, umask should be specified as an octal *string*, not an octal (or decimal) *integer*.
Per @abadger remarks in #43256, we should avoid documenting buggy behavior.
+label: docsite_pr
SUMMARY
Remove documentation that supplying an integer for the pip umask option "works, but was almost certainly not what was intended."
Fixes #43256
ISSUE TYPE
COMPONENT NAME
pip