[issue26352] getpass incorrectly displays password prompt on stderr on fallback

R. David Murray added the comment: stdout is much more likely to be redirected than stderr, so falling back to stderr makes more sense than falling back to stdout. In the normal case, the prompt is shown regardless of whether stdout is redirected, and we're trying our best to replicate that i

[issue26352] getpass incorrectly displays password prompt on stderr on fallback

Changes by Serhiy Storchaka : -- nosy: +serhiy.storchaka status: open -> pending ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue26352] getpass incorrectly displays password prompt on stderr on fallback

Martin Panter added the comment: Why do you think using stderr is bad behaviour, or that a user would want the prompt and warning on different streams? As far as I can tell, the documentation already says that stderr is used by default, and there are other unpatched references to sys.stderr le

[issue26352] getpass incorrectly displays password prompt on stderr on fallback

Matt Hooks added the comment: Patch attached. I'm unsure whether forcing the warning message to stderr is the right choice here, but it seems unlikely that users would want their warning and password prompt on the same stream. The alternative here would be a second kwarg, but that seems over

[issue26352] getpass incorrectly displays password prompt on stderr on fallback

Changes by Ethan Furman : -- nosy: +ethan.furman ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue26352] getpass incorrectly displays password prompt on stderr on fallback

New submission from Matt Hooks: When calling getpass.getpass(), certain circumstances cause it to fallback to getpass.fallback_getpass, such as when swapping out sys.stdin for another object in a unit test. In such a circumstance, fallback_getpass may be called with stream=None when getpass i