-
Notifications
You must be signed in to change notification settings - Fork 0
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
make them private #117
make them private #117
Conversation
I'm fine with this change, but I think what it accomplishes is actually to make these methods public but in a different module. Rather than |
I thought that the distinction private public for us is just what is documented vs what is not. I am happy to prepend underscore but that still does not make private :) |
"python private" I guess. There's not real privacy in python, but prepending an underscore prevents them from being imported with |
Did some googling and it looks like pdoc ignores methods that start with I don't see anything in the docs which would make utils explicitly private. |
To clarify, I think it's OK to have these functions in utils and to have them be public but undocumented. I also think it's OK to make them private in the sense of adding an underscore. However, I do not think that we should have them in utils and have them be private because having them in utils requires that they be imported and used outside of the scope in which they're defined. If we make them private, we should make them private to the module in which they're used. Does that make sense? |
I agree about prepending with the _. I think if we make these changes we are good. |
so @jtencer do you want me to make them private inside the file where they are used or leave them where they are ? |
I'm good with it now |
@fnrizzi please ping me if you'd like me to resolve the conflict. |
superseeded by #122 |
No description provided.