Problem:

`glob.glob` documentation states that "pathname ... can contain shell-style wildcards." 

However, it stops short of saying that shell-style wildcards are handled the same way as in a POSIX-compliant/friendly shell.

https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_13_02 POSIX requires that "`*` (asterisk) is a pattern that shall match any string, including the null string."

However, `glob.glob` pattern `*` (asterisk) doesn't match an empty/null string. 

Reproduction:

$ ls *.bash_profile
.bash_profile
$ python3 -c 'import glob; print(glob.glob("*.bash_profile"))'
[]
$ python3 -c 'import glob; print(glob.glob(".bash_profile"))'
['.bash_profile']

Only pattern beginning with a dot can match filename beginning with a dot.

From https://docs.python.org/3/library/glob.html

   Note that unlike fnmatch.fnmatch(), glob treats filenames beginning with a dot (.) as special cases.

This phrase was added in issue16695 in attempt to improve documentation, but it is still not clear.

I may be naive, but why then:

$ python3 -c 'from pathlib import Path; print(list(Path(".").glob("*.bash_profile")))'

Outputs:

[PosixPath('.bash_profile')]


?

Sadly, this because pathlib glob and glob.glob use different implementations. And glob.glob does not provide something equivalent to a DOTALL flag allowing a user to glob hidden files without explicitly defining the leading dot in the pattern.

> glob.glob does not provide something equivalent to a DOTALL flag 

I see now, said a blind man.