Flexibility in setting Python protection #6555
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Python does not have a real knowledge of protection in respect to variables and functions (i.e. public / private / protected). There are some ad-hoc rules but they changed over time as well.
Doxygen uses some build in settings for protection i.e. methods starting with '__' and ending with '__' are public other variables and methods starting with '_' are private. This change makes it possible for the user to define his own rules for the protection within Python.
(Loosely based on issue #6554)