We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In quite some places the return type of functions is specified like this:
Returns ------- swapped : type of caller (new object)
Pycharm now thinks the function returns an object of type type and warns about legitimate usage.
type
See #17079 for a related issue.
The problem could be mitigated by a wording avoiding any actual type as the first word. Proposal how the change could look like: #21623
The text was updated successfully, but these errors were encountered:
DOC: Do no use 'type' as fist word when specifying a return type (pan…
7214e63
…das-dev#21622) Pycharm is otherwise confused and expects objects of type 'type' to be returned.
DOC: Do no use 'type' as first word when specifying a return type (pa…
452cd99
…ndas-dev#21622) Pycharm is otherwise confused and expects objects of type 'type' to be returned.
DOC: Do no use 'type' as first word when specifying a return type (#2…
3433f19
…1622) (#21623)
9432e3c
…ndas-dev#21622) (pandas-dev#21623)
Successfully merging a pull request may close this issue.
Problem description
In quite some places the return type of functions is specified like this:
Pycharm now thinks the function returns an object of type
type
and warns about legitimate usage.See #17079 for a related issue.
The problem could be mitigated by a wording avoiding any actual type as the first word.
Proposal how the change could look like: #21623
The text was updated successfully, but these errors were encountered: