Version 1.0

[lovelydinosaur]

Proposal for httpcore version 1.0.

Our API is already stable, and I don't think we've any blockers that ought to prevent us issuing a 1.0 release.

The one change that I am suggesting in this pull request is that we switch to a more minimal set of default dependancies, by making the async case fully optional. We've already done the work on making these packages not strictly required. This proposal builds on that work by no longer installing anyio/sniffio/trio by default.

---

TODO:

• Update CHANGELOG.md

---

See also https://github.com/encode/httpx/issues/947.

[karpetrosyan]

Do we want #800 after this release?

[lovelydinosaur]

Do we want #800 after this release?

Have followed up against that discussion.

[karpetrosyan]

We can change the error message in https://github.com/encode/httpcore/pull/809/files#diff-5bb436aadeb1bfe2f41078fe8d1a4db589eb3405df644e07ce5e26c7749da824R40 to something like Running under trio requires the 'httpcore' to be installed with the 'trio' extra. because when the user has trio installed, the current message doesn't make any sense.

[zanieb]

because when the user has trio installed, the current message doesn't make any sense

Why would that error be displayed when trio is installed?

[karpetrosyan]

because when the user has trio installed, the current message doesn't make any sense

Why would that error be displayed when trio is installed?

When the trio is installed but the sniffio isn't

See: https://github.com/encode/httpcore/pull/809/files#diff-5bb436aadeb1bfe2f41078fe8d1a4db589eb3405df644e07ce5e26c7749da824R20-R24

[lovelydinosaur]

We can change the error message

Resolved

[lovelydinosaur]

I think we're good to go here... I'll plan on releasing this tomorrow.

[karpetrosyan]

Do we want to include #799 to 1.0.0?

[lovelydinosaur]

Ok.

[karpetrosyan]

Release date 🥶

[lovelydinosaur]

Oops. (thanks)

[agronholm]

On that note, how are you creating your GitHub releases? I don't see any automation.

[lovelydinosaur]

Copy the release notes. Yup some buttons do get pressed through the GitHub UI.
From that, the PyPI releases are automated from a GitHub action.

[agronholm]

In case you're interested, here's how I handle things: https://github.com/agronholm/anyio/blob/master/.github/workflows/publish.yml
Pushing a tag makes the automation copy the release notes matching the tag, and make a GitHub release as well as publishing the sdist and wheels to PyPI.