[nit] reorder the experimental features in command_line.rst #20171
+9
−9
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The documentation lists these in the order
PreciseTupleTypes,InlineTypedDict, but mypy --help lists them in the orderInlineTypedDict,PreciseTupleTypes. This updates the documentation to match the --help listing (including putting the descriptions in the same order as the names). This is the superior order, because it is alphabetical. Therefore, people will know where to look. This is sorted on purpose in the --help code, by the way; it's not just a coincidence.outdated claim
I notice that mypy --help now also lists TypeForm as an enablable experimental feature. This PR does not document that, but if anyone ever does, I sure know where they should put that section relative to these other two items!