Skip to content

Conversation

@hauntsaninja
Copy link
Collaborator

I've now seen a few different times people misunderstand exactly what spec conformance implies, so here's a PR adding a small disclaimer

@srittau srittau added the topic: conformance tests Issues with the conformance test suite label Jan 20, 2026
<h3>Python Type System Conformance Test Results</h3>
<p class="disclaimer">
While spec conformance is important for the ecosystem, we don't recommend using it
as the primary basis for choosing a type checker. It is not (and is not meant to be)
Copy link
Member

Choose a reason for hiding this comment

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

This second sentence feels a bit too strong for me. Sure, a lot of the conformance suite is about esoteric topics that don't affect users much, and there are many important aspects of a practical type checker that aren't reflected in the conformance suite, but I do believe that spec conformant behavior should be user-friendly behavior.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Okay, tried a reword

Copy link
Member

@carljm carljm left a comment

Choose a reason for hiding this comment

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

The new wording seems fine to me. (It looks like the actual results haven't been re-generated with the new wording, though.)

@hauntsaninja hauntsaninja merged commit 20096ee into python:main Jan 22, 2026
4 checks passed
@hauntsaninja hauntsaninja deleted the disclaim branch January 22, 2026 00:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

topic: conformance tests Issues with the conformance test suite

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants