Seth Michael Larson

[Per Python 3.7's documentation](https://docs.python.org/3/library/ssl.html#ssl.PROTOCOL_TLSv1_2) there won't be a `PROTOCOL_TLSv1_3` definition in the `ssl` module. To force the use TLSv1.3 in Python you have to do `PROTOCOL_TLS | OP_NO_TLSv1_2 | OP_NO_TLSv1_1...

@hugovk Probably to distinguish between 0 downloads and not-yet-released. However I don't think I've seen a single project with zero downloads on release day due to scrapers / mirrors. :)

This feature will become more in demand as time goes on. One of the requirements for OpenSSF Scorecard is pinned development dependencies with versions and hashes. Without support in pip-tools...

This can be closed with #181

@nir0s Can you close this issue? Thanks

To make things easier for us and more consistent across multiple tools imo we should treat bugs in /etc/*-release files as bugs upstream instead of something actionable in Distro. Thoughts...

I'm not sure that this fix is needed though, wouldn't we see more chatter / +1s on this issue if there were widespread problems with distributions identifying incorrectly? Quoting @nir0s...

Maybe? What does running `uname -a` print on those platforms?

I would suggest changing `linux_distribution()` to just `distribution()`? The rest map pretty well actually. All Windows and Mac distributions have a codename, id='windows', 'macos', version, name, pretty name.

I'd say that something like that would work fine. Do we only define that method when on Linux (forcing `distro` users to check with `hasattr`) or have `linux_distribution` throw an...