Skip to content

Document how evil --no-strict-optional is#16731

Merged
hauntsaninja merged 1 commit intopython:masterfrom
hauntsaninja:strict-optional
Jan 2, 2024
Merged

Document how evil --no-strict-optional is#16731
hauntsaninja merged 1 commit intopython:masterfrom
hauntsaninja:strict-optional

Conversation

@hauntsaninja
Copy link
Copy Markdown
Collaborator

On multiple occasions, I've encountered folks using this, running into issues and then being perplexed when they figure out what --no-strict-optional actually does. Most recently in #16718 (comment)

This is a non-standard, dangerous option that should not be used in modern typed Python. It's been five and a half years since it was the default behaviour in mypy, so we should deemphasise and warn about its existence.

On multiple occasions, I've encountered folks using this, running into
issues and then being perplexed when they figure out what
`--no-strict-optional` actually does. Most recently in
python#16718 (comment)

This is a non-standard, dangerous option that should not be used in
modern typed Python. It's been five and a half years since it was the
default behaviour in mypy, so we should deemphasise and warn about its
existence.
@hauntsaninja hauntsaninja merged commit a1b4e32 into python:master Jan 2, 2024
@hauntsaninja hauntsaninja deleted the strict-optional branch January 2, 2024 21:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants