… to be a char literal.
…ke any handle that use case.
…oduction code in these cases and wasn't properly imported either.
We should never throw Errors on malformed data - especially since the module does not provide validation facilities. Base64 is widely used on the web, so encoded strings need to be treated like user input. The added unittests are purposefully vague. This is to allow changing the implementation within the spec (whether to throw, ignore or try parsing trailing bytes).
…h standard functional programming terminology.
The reason for this change is the quirky behavior of access for SUID programs: a file may not appear to "exist", despite that the program would be able to open it just fine. The behavior in question is described as follows in the access man page: > The check is done using the calling process's real UID and GID, rather > than the effective IDs as is done when actually attempting an operation > (e.g., open(2)) on the file. This allows set-user-ID programs to easily > determine the invoking user's authority. While various operating systems provide eaccess or euidaccess functions, these are not part of POSIX - so it's safer to use stat instead.