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
bpo-44752: Make rlcompleter not call @property
methods
#27401
Conversation
* rlcompleter was calling these methods to identify whether to add parenthesis to the completion, based on if the attribute is callable. * for property objects, completion with parenthesis are never desirable. * property methods with print statements behaved very strangely, which was especially unfriendly to language newcomers. <tab> could suddenly produce output unexpectedly.
@ambv, I see what you mean now about that change weakening the test. I created a new test case, and revised the original one to use the original assertions, now using |
@property
methods@property
methods
Thanks @jdevries3133 for the PR, and @ambv for merging it |
) * rlcompleter was calling these methods to identify whether to add parenthesis to the completion, based on if the attribute is callable. * for property objects, completion with parenthesis are never desirable. * property methods with print statements behaved very strangely, which was especially unfriendly to language newcomers. <tab> could suddenly produce output unexpectedly. (cherry picked from commit 50de8f7) Co-authored-by: Jack DeVries <58614260+jdevries3133@users.noreply.github.com>
GH-27444 is a backport of this pull request to the 3.10 branch. |
) * rlcompleter was calling these methods to identify whether to add parenthesis to the completion, based on if the attribute is callable. * for property objects, completion with parenthesis are never desirable. * property methods with print statements behaved very strangely, which was especially unfriendly to language newcomers. <tab> could suddenly produce output unexpectedly. (cherry picked from commit 50de8f7) Co-authored-by: Jack DeVries <58614260+jdevries3133@users.noreply.github.com>
GH-27445 is a backport of this pull request to the 3.9 branch. |
…H-27444) * rlcompleter was calling these methods to identify whether to add parenthesis to the completion, based on if the attribute is callable. * for property objects, completion with parenthesis are never desirable. * property methods with print statements behaved very strangely, which was especially unfriendly to language newcomers. <tab> could suddenly produce output unexpectedly. (cherry picked from commit 50de8f7) Co-authored-by: Jack DeVries <58614260+jdevries3133@users.noreply.github.com>
…27445) * rlcompleter was calling these methods to identify whether to add parenthesis to the completion, based on if the attribute is callable. * for property objects, completion with parenthesis are never desirable. * property methods with print statements behaved very strangely, which was especially unfriendly to language newcomers. <tab> could suddenly produce output unexpectedly. (cherry picked from commit 50de8f7) Co-authored-by: Jack DeVries <58614260+jdevries3133@users.noreply.github.com>
parenthesis to the completion, based on if the attribute is callable.
was especially unfriendly to language newcomers. could suddenly
produce output unexpectedly.
https://bugs.python.org/issue44752