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

Add option to hide __ members from auto complete. #168

Closed
karthiknadig opened this issue Oct 18, 2021 · 2 comments · Fixed by #169
Closed

Add option to hide __ members from auto complete. #168

karthiknadig opened this issue Oct 18, 2021 · 2 comments · Fixed by #169
Labels
enhancement New feature or request

Comments

@karthiknadig
Copy link
Contributor

For microsoft/vscode-python#17776

@pappasam
Copy link
Owner

pappasam commented Oct 19, 2021

@karthiknadig does this feature request only apply to class attributes / methods that begin with __ but that do not end with __? For example, __init__ technically begins with __ but the __init__ method is different from something like __private_attribute. See https://docs.python.org/3/tutorial/classes.html#private-variables.

This leads me to another design question: do we want to support removing either private variable completion (single underscore start followed by non-underscore) and mangled private variable completion (double underscore start, at most single underscore finish)?

@pappasam pappasam added the enhancement New feature or request label Oct 19, 2021
@karthiknadig
Copy link
Contributor Author

The feature request applies to all variables that have __something and __init__ patterns.

If we have levels of filtering or regex patterns, I think, that would work better, this way we can control the behavior of flags like python.autoComplete.showAdvancedMembers from the IDE. So, if we want to change the meaning of true to include since-underscore variables.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants