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

Differentiate public and private API #101

Closed
jpgill86 opened this issue Jul 26, 2019 · 0 comments · Fixed by #104
Closed

Differentiate public and private API #101

jpgill86 opened this issue Jul 26, 2019 · 0 comments · Fixed by #104
Milestone

Comments

@jpgill86
Copy link
Owner

Decide which functions and classes should definitely be public-facing, get their call signatures into a form I'm happy with, and commit to avoiding changing them. Other function names should start with underscore to prevent them from importing from each module and to indicate they may change in the future.

@jpgill86 jpgill86 added this to the 0.8.0 milestone Jul 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant