Make Distribution class public

[jaraco]

In GitLab by @warsaw on Dec 19, 2018, 22:47

[jaraco]

In GitLab by @warsaw on Dec 19, 2018, 22:47

mentioned in merge request !31

[jaraco]

In GitLab by @warsaw on Dec 19, 2018, 23:10

Let's make a final decision about whether this class should be public and documented. We can defer this until closer to the Python 3.8 release (since we'll be including this in the 3.8 stdlib).

[jaraco]

In GitLab by @jaraco on Feb 14, 2019, 15:53

Looking at #45, we have a user requesting access to the distribution() function, which implicitly requests for visibility to the Distribution class. I think we may want to expose it, but provisionally such that its interface is less rigid than the API functions.

[jaraco]

In GitLab by @jaraco on Feb 23, 2019, 15:11

changed title from {-Should the Distribution class be public?-} to {+Make Distribution class public+}

[jaraco]

In GitLab by @jaraco on Feb 23, 2019, 15:32

Here's how I'd like to proceed - let's document the Distribution class and explicitly whitelist the supported APIs.

[jaraco]

In GitLab by @warsaw on Feb 23, 2019, 23:48

What about making Distribution a full ABC (it's kind of partly one right now), and exposing that? Then the thing that distributions() returns would be an implementation of the ABC. I don't mind if there's some name juggling here, but the basic idea of exposing an interface rather than a specific implementation is what I have in mind.

[jaraco]

In GitLab by @warsaw on May 6, 2019, 14:22

Pycon 2019 sprint decision: let's expose Distribution as a public API and remove the caveats.

[jaraco]

In GitLab by @warsaw on May 6, 2019, 14:22

assigned to @jaraco

[jaraco]

In GitLab by @jaraco on May 6, 2019, 16:26

mentioned in commit 8a98c285302659eb1d9ff6f01cb132904d7de71e

[jaraco]

In GitLab by @warsaw on May 6, 2019, 19:08

closed via merge request !53

[jaraco]

In GitLab by @warsaw on May 6, 2019, 19:08

mentioned in commit 9092fa9