I'm using the --no-private-names option, yet I'm
seeing __init__.py in my list of modules. Shouldn't
this count as a private name?
Logged In: YES
No, __init__.py wouldn't match the private name rule. The pattern for
method names is based on the Python definition (any name starting with
at least 2 underscores and **NOT** ending with 2 underscores). I don't
remember if that rule is even applied to file names, though.
Log in to post a comment.