This has been true since Python 1.x.  getpass.getuser() is documented as "raising an exception" but doesn't specify what exception.

On Windows when the environment variables it looks at are not set, an ImportError (!) escapes due to "import pwd" failing.  It could just a easily allow an exception from the following pwd.getpwuid(os.getuid())[0] call to escape on systems when pwd exists.

None of these are actually helpful to the caller as they are left having to catch a bare Exception around a getpass.getuser() call to take another course of action.  I filed this as I just saw someone suggesting code that specifically catches ImportError on getpass.getuser().

It is too late to change the exception type coming out in 2.7 or 3.6, but cleaning up this underspecified behavior to be a meaningful exception for 3.7 seems reasonable.

What kind of exception did you have in mind? As the 'someone' you mentioned, I can contribute this.

btw, os.getuid() on windows raises an attribute error, so we need to check that too.

Hi. I've updated the docs.

I'm wondering if the code needs to be patched as well. Essentially we should raise a unified Exception for unable to get the username I suppose?

Please let me know if you have any comments/suggestions on wording. Thanks.

Hi,

For the wording, I have no suggestions but seems to be fine.

For the rest, I think you have modified the documentation and it's fine and we don't talk about the code.

We could merge the PR for the documentation and maybe you could create a new PR for the code.