Skip to content

Conversation

@bluetech
Copy link
Member

Maybe it can increase adoption.

@bluetech bluetech added the skip news used on prs to opt out of the changelog requirement label Oct 27, 2025
Copy link
Member

@Pierre-Sassoulas Pierre-Sassoulas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👌

Copy link
Member

@The-Compiler The-Compiler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yay, looks great overall!

See the :confval:`strict` for the options it enables and their effect.

If pytest adds new strictness options in the future, they will also be enabled by ``strict``.
Therefore, you should only use ``strict`` if you use a locked version of pytest,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Therefore, you should only use ``strict`` if you use a locked version of pytest,
Therefore, you should only use ``strict`` if you use a pinned version of pytest,

maybe?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think both terms are used, so I went with "pinned/locked".

.. _`strict mode`:

Using pytest's strict mode
--------------------------
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this maybe have a versionadded directive, and/or a quick blurb on how to achieve the same result with older pytest versions?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added the versionadded. I didn't add how to achieve in previous versions, hopefully can be understood by following the links.

@bluetech bluetech force-pushed the strict-good-practice branch from b263229 to d68eba9 Compare October 28, 2025 10:19
@bluetech
Copy link
Member Author

Thanks for the reviews. I also sync'd the text in the reference/changelog/goodpractice.

@bluetech bluetech merged commit f628f43 into pytest-dev:main Oct 28, 2025
33 checks passed
@bluetech bluetech deleted the strict-good-practice branch October 28, 2025 16:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip news used on prs to opt out of the changelog requirement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants