Fix 3605

[RonnyPfannschmidt]

Thanks for submitting a PR, your contribution is really appreciated!

Here's a quick checklist that should be present in PRs (you can delete this text from the final description, this is
just a guideline):

• Create a new changelog file in the changelog folder, with a name like <ISSUE NUMBER>.<TYPE>.rst. See changelog/README.rst for details.
• Target the master branch for bug fixes, documentation updates and trivial changes.
• Target the features branch for new features and removals/deprecations.
• Include documentation when adding new features.
• Include new tests or update existing tests when applicable.

Unless your change is trivial or a small documentation fix (e.g., a typo or reword of a small section) please:

• Add yourself to AUTHORS in alphabetical order;

[coveralls]

Coverage increased (+0.05%) to 92.694% when pulling 2c50f4c on RonnyPfannschmidt:fix-3605 into e86fe38 on pytest-dev:master.

[nicoddemus]

How can we phrase this in a way that end users (that don't know the internals) can understand? 🤔

[nicoddemus]

Please add a docstring here explaining why this is needed

[nicoddemus]

btw, I don't think GitHub looks at the title of the PR to automatically close issues:

You can include keywords in your pull request descriptions, as well as commit messages, to automatically close issues in GitHub.

https://help.github.com/articles/closing-issues-using-keywords/

😉

edit: I just noticed that your last commit does include "fix " so this is of course fine. 😁