Create a symlink that points to file that doesn't exist:

    ln -s /nonexisting_file my_symlink

Then try to glob for that symlink from Python using pathlib:

    python3
    >>> import pathlib
    >>> list(pathlib.Path(".").glob("my_symlink"))
    []
    >>> list(pathlib.Path(".").glob("my_symlink*"))
    [PosixPath('my_symlink')]

I'm a bit surprised that these two globs do not return the same results. Personally I would expect both to find the symlink.

Is this behaviour a bug or is it intentional?

The issue is that _PreciseSelector follows the symlink when it checks if a path exists before yielding it as a result.

I've put up a PR with a fix; I've also added a *follow_symlinks* arg to `exists()` method because it seems more logical to be able to test if a path exists via the same method rather than having to also remember and to check for it being a symlink.

I will add docs and news a bit later today or tomorrow.

Rasmus: thanks for the report, it does seem like a bug to me.

By the way note that path.glob('**/my_symlink') also does return the dangling symlink match. And glob.glob('my_symlink') also returns a dangling symlink.