Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify documentation for typing extension #4549

Merged
merged 2 commits into from
Jun 10, 2021

Conversation

cdce8p
Copy link
Member

@cdce8p cdce8p commented Jun 7, 2021

Description

Clarify documentation for typing extension.

Type of Changes

Type
βœ“ πŸ“œ Docs

Related Issue

Closes #4545

@coveralls
Copy link

coveralls commented Jun 7, 2021

Coverage Status

Coverage remained the same at 91.879% when pulling 61ac49f on cdce8p:docs-typing-ext into 2a186f4 on PyCQA:master.

"3.7 - 3.9"
"Set to ``no`` if the app / library does NOT need to "
"support runtime introspection of type annotations. "
"Only change it if you understand what that means. "
Copy link
Member

Choose a reason for hiding this comment

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

Could we explain "what that means" or link to the doc that explains it here ? :)

Copy link
Member Author

Choose a reason for hiding this comment

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

My initial idea was something along the lines:

If you don't know what that means, you're probably better off to leave it as is.

I just wasn't sure this would be the right tone. It's never the less true. This should really only be set if the user fully understands the consequences. Not knowing runtime introspection is a clear signal that he/she doesn't know enough.

Copy link
Member

Choose a reason for hiding this comment

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

Sure, but this is the place where we should link to where you need to look if you want to try to understand, no ?

Copy link
Member Author

Choose a reason for hiding this comment

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

@Pierre-Sassoulas I've updated the explanation. Please take a look and let me know what you think

@cdce8p cdce8p added this to the 2.9.0 milestone Jun 7, 2021
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.

Nice, thank you for making this clearer !

@Pierre-Sassoulas Pierre-Sassoulas merged commit 90d8a90 into pylint-dev:master Jun 10, 2021
@cdce8p cdce8p deleted the docs-typing-ext branch June 10, 2021 05:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When to set runtime-typing to no?
3 participants