Skip to content

Document our public API #307

Closed
Closed
@gsnedders

Description

@gsnedders

For semver to make any sense, we really need to actually define what our public API is. We probably want to do this both through documentation and through the de-facto Python standard of underscore-prefixing (though that will likely break stuff again, le sight, but if people are using the private API they'll likely complain when we do break it in some 1.x release).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions