Deploy httpcore2 docs as a standalone site

.github/workflows/main.yml

@@ -81,17 +81,28 @@ jobs:
         run: scripts/install
 
       - name: Build docs
-        run: uv run zensical build --clean
+        run: uv run zensical build --clean -f docs/httpx2/mkdocs.yml
+
+      - name: Build httpcore2 docs
+        run: uv run zensical build --clean -f docs/httpcore2/mkdocs.yml
 
       - uses: cloudflare/wrangler-action@ebbaa1584979971c8614a24965b4405ff95890e0 # v4.0.0
         id: deploy
         with:
           apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
           accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
-          command: versions upload --tag pr-${{ github.event.pull_request.number }}
+          command: versions upload --config docs/httpx2/wrangler.toml --tag pr-${{ github.event.pull_request.number }}
+
+      - uses: cloudflare/wrangler-action@ebbaa1584979971c8614a24965b4405ff95890e0 # v4.0.0
+        id: deploy-httpcore2
+        with:
+          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
+          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
+          command: versions upload --config docs/httpcore2/wrangler.toml --tag pr-${{ github.event.pull_request.number }}
 
       - name: Comment preview URL
         uses: marocchino/sticky-pull-request-comment@0ea0beb66eb9baf113663a64ec522f60e49231c0 # v3.0.4
         with:
           message: |
             **Docs preview:** ${{ steps.deploy.outputs.deployment-url }}
+            **httpcore2 docs preview:** ${{ steps.deploy-httpcore2.outputs.deployment-url }}

.github/workflows/publish.yml

@@ -45,7 +45,13 @@ jobs:
         uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
         with:
           name: documentation
-          path: site/
+          path: docs/httpx2/site/
+
+      - name: Upload httpcore2 documentation
+        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+        with:
+          name: documentation-httpcore2
+          path: docs/httpcore2/site/
 
   publish:
     runs-on: ubuntu-latest
@@ -87,10 +93,38 @@ jobs:
         uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
         with:
           name: documentation
-          path: site/
+          path: docs/httpx2/site/
+
+      - uses: cloudflare/wrangler-action@ebbaa1584979971c8614a24965b4405ff95890e0 # v4.0.0
+        with:
+          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
+          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
+          command: deploy --config docs/httpx2/wrangler.toml
+
+  docs-cloudflare-httpcore2:
+    runs-on: ubuntu-latest
+    needs: build
+
+    permissions:
+      contents: read
+
+    environment:
+      name: cloudflare
+      url: https://httpcore2.pydantic.dev
+
+    steps:
+      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        with:
+          persist-credentials: false
+
+      - name: Download artifacts
+        uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
+        with:
+          name: documentation-httpcore2
+          path: docs/httpcore2/site/
 
       - uses: cloudflare/wrangler-action@ebbaa1584979971c8614a24965b4405ff95890e0 # v4.0.0
         with:
           apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
           accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
-          command: deploy
+          command: deploy --config docs/httpcore2/wrangler.toml

src/httpcore2/docs/async.md → docs/httpcore2/docs/async.md

@@ -13,13 +13,13 @@ Launching concurrent async tasks is far more resource efficient than spawning mu
 If you're using async with [Python's stdlib `asyncio` support](https://docs.python.org/3/library/asyncio.html), install the optional dependencies using:
 
 ```shell
-pip install 'httpcore[asyncio]'
+pip install 'httpcore2[asyncio]'
 ```
 
 Alternatively, if you're working with [the Python `trio` package](https://trio.readthedocs.io/en/stable/):
 
 ```shell
-pip install 'httpcore[trio]'
+pip install 'httpcore2[trio]'
 ```
 
 We highly recommend `trio` for async support. The `trio` project [pioneered the principles of structured concurrency](https://en.wikipedia.org/wiki/Structured_concurrency), and has a more carefully constrained API against which to work from.
@@ -29,21 +29,21 @@ We highly recommend `trio` for async support. The `trio` project [pioneered the
 When using async support, you need make sure to use an async connection pool class:
 
 ```python
-# The async variation of `httpcore.ConnectionPool`
-async with httpcore.AsyncConnectionPool() as http:
+# The async variation of `httpcore2.ConnectionPool`
+async with httpcore2.AsyncConnectionPool() as http:
     ...
 ```
 
 ### Sending requests
 
-Sending requests with the async version of `httpcore` requires the `await` keyword:
+Sending requests with the async version of `httpcore2` requires the `await` keyword:
 
 ```python
 import asyncio
-import httpcore
+import httpcore2
 
 async def main():
-    async with httpcore.AsyncConnectionPool() as http:
+    async with httpcore2.AsyncConnectionPool() as http:
         response = await http.request("GET", "https://www.example.com/")
 
 
@@ -65,11 +65,11 @@ For example:
 
 ```python
 import asyncio
-import httpcore
+import httpcore2
 
 
 async def main():
-    async with httpcore.AsyncConnectionPool() as http:
+    async with httpcore2.AsyncConnectionPool() as http:
         async with http.stream("GET", "https://www.example.com/") as response:
             async for chunk in response.aiter_stream():
                 print(f"Downloaded: {chunk}")
@@ -80,10 +80,10 @@ asyncio.run(main())
 
 ### Pool lifespans
 
-When using `httpcore` in an async environment it is strongly recommended that you instantiate and use connection pools using the context managed style:
+When using `httpcore2` in an async environment it is strongly recommended that you instantiate and use connection pools using the context managed style:
 
 ```python
-async with httpcore.AsyncConnectionPool() as http:
+async with httpcore2.AsyncConnectionPool() as http:
     ...
 ```
 
@@ -93,7 +93,7 @@ If you do want to use a connection pool without this style then you'll need to e
 
 ```python
 try:
-    http = httpcore.AsyncConnectionPool()
+    http = httpcore2.AsyncConnectionPool()
     ...
 finally:
     await http.aclose()
@@ -117,7 +117,7 @@ Let's take a look at sending several outgoing HTTP requests concurrently, using
 
 ```python
 import asyncio
-import httpcore
+import httpcore2
 import time
 
 
@@ -126,7 +126,7 @@ async def download(http, year):
 
 
 async def main():
-    async with httpcore.AsyncConnectionPool() as http:
+    async with httpcore2.AsyncConnectionPool() as http:
         started = time.time()
         # Here we use `asyncio.gather()` in order to run several tasks concurrently...
         tasks = [download(http, year) for year in range(2000, 2020)]
@@ -146,7 +146,7 @@ asyncio.run(main())
 Trio is [an alternative async library](https://trio.readthedocs.io/en/stable/), designed around the [the principles of structured concurrency](https://en.wikipedia.org/wiki/Structured_concurrency).
 
 ```python
-import httpcore
+import httpcore2
 import trio
 import time
 
@@ -156,7 +156,7 @@ async def download(http, year):
 
 
 async def main():
-    async with httpcore.AsyncConnectionPool() as http:
+    async with httpcore2.AsyncConnectionPool() as http:
         started = time.time()
         async with trio.open_nursery() as nursery:
             for year in range(2000, 2020):
@@ -178,7 +178,7 @@ AnyIO is an [asynchronous networking and concurrency library](https://anyio.read
 The `anyio` library is designed around the [the principles of structured concurrency](https://en.wikipedia.org/wiki/Structured_concurrency), and brings many of the same correctness and usability benefits that Trio provides, while interoperating with existing `asyncio` libraries.
 
 ```python
-import httpcore
+import httpcore2
 import anyio
 import time
 
@@ -188,7 +188,7 @@ async def download(http, year):
 
 
 async def main():
-    async with httpcore.AsyncConnectionPool() as http:
+    async with httpcore2.AsyncConnectionPool() as http:
         started = time.time()
         async with anyio.create_task_group() as task_group:
             for year in range(2000, 2020):
@@ -207,9 +207,9 @@ anyio.run(main)
 
 # Reference
 
-## `httpcore.AsyncConnectionPool`
+## `httpcore2.AsyncConnectionPool`
 
-::: httpcore.AsyncConnectionPool
+::: httpcore2.AsyncConnectionPool
     handler: python
     rendering:
         show_source: False

src/httpcore2/docs/connection-pools.md → docs/httpcore2/docs/connection-pools.md

@@ -1,15 +1,15 @@
 # Connection Pools
 
-While the top-level API provides convenience functions for working with `httpcore`,
+While the top-level API provides convenience functions for working with `httpcore2`,
 in practice you'll almost always want to take advantage of the connection pooling
 functionality that it provides.
 
 To do so, instantiate a pool instance, and use it to send requests:
 
 ```python
-import httpcore
+import httpcore2
 
-http = httpcore.ConnectionPool()
+http = httpcore2.ConnectionPool()
 r = http.request("GET", "https://www.example.com/")
 
 print(r)
@@ -21,11 +21,11 @@ Connection pools support the same `.request()` and `.stream()` APIs [as describe
 We can observe the benefits of connection pooling with a simple script like so:
 
 ```python
-import httpcore
+import httpcore2
 import time
 
 
-http = httpcore.ConnectionPool()
+http = httpcore2.ConnectionPool()
 for counter in range(5):
     started = time.time()
     response = http.request("GET", "https://www.example.com/")
@@ -52,7 +52,7 @@ The connection pool instance is also the main point of configuration. Let's take
 ### SSL configuration
 
 * `ssl_context`: An SSL context to use for verifying connections.
-                 If not specified, the default `httpcore.default_ssl_context()`
+                 If not specified, the default `httpcore2.default_ssl_context()`
                  will be used.
 
 ### Pooling configuration
@@ -93,20 +93,20 @@ Working with a single global instance isn't a bad idea for many use case, since
 # This is perfectly fine for most purposes.
 # The connection pool will automatically be closed when it is garbage collected,
 # or when the Python interpreter exits.
-http = httpcore.ConnectionPool()
+http = httpcore2.ConnectionPool()
 ```
 
 However, to be more explicit around the resource usage, we can use the connection pool within a context manager:
 
 ```python
-with httpcore.ConnectionPool() as http:
+with httpcore2.ConnectionPool() as http:
     ...
 ```
 
 Or else close the pool explicitly:
 
 ```python
-http = httpcore.ConnectionPool()
+http = httpcore2.ConnectionPool()
 try:
     ...
 finally:
@@ -115,17 +115,17 @@ finally:
 
 ## Thread and task safety
 
-Connection pools are designed to be thread-safe. Similarly, when using `httpcore` in an async context connection pools are task-safe.
+Connection pools are designed to be thread-safe. Similarly, when using `httpcore2` in an async context connection pools are task-safe.
 
 This means that you can have a single connection pool instance shared by multiple threads.
 
 ---
 
 # Reference
 
-## `httpcore.ConnectionPool`
+## `httpcore2.ConnectionPool`
 
-::: httpcore.ConnectionPool
+::: httpcore2.ConnectionPool
     handler: python
     rendering:
         show_source: False

src/httpcore2/docs/connections.md → docs/httpcore2/docs/connections.md

@@ -6,23 +6,23 @@ TODO
 
 # Reference
 
-## `httpcore.HTTPConnection`
+## `httpcore2.HTTPConnection`
 
-::: httpcore.HTTPConnection
+::: httpcore2.HTTPConnection
     handler: python
     rendering:
         show_source: False
 
-## `httpcore.HTTP11Connection`
+## `httpcore2.HTTP11Connection`
 
-::: httpcore.HTTP11Connection
+::: httpcore2.HTTP11Connection
     handler: python
     rendering:
         show_source: False
 
-## `httpcore.HTTP2Connection`
+## `httpcore2.HTTP2Connection`
 
-::: httpcore.HTTP2Connection
+::: httpcore2.HTTP2Connection
     handler: python
     rendering:
         show_source: False

docs/httpcore2/docs/exceptions.md

@@ -0,0 +1,18 @@
+# Exceptions
+
+The following exceptions may be raised when sending a request:
+
+* `httpcore2.TimeoutException`
+    * `httpcore2.PoolTimeout`
+    * `httpcore2.ConnectTimeout`
+    * `httpcore2.ReadTimeout`
+    * `httpcore2.WriteTimeout`
+* `httpcore2.NetworkError`
+    * `httpcore2.ConnectError`
+    * `httpcore2.ReadError`
+    * `httpcore2.WriteError`
+* `httpcore2.ProtocolError`
+    * `httpcore2.RemoteProtocolError`
+    * `httpcore2.LocalProtocolError`
+* `httpcore2.ProxyError`
+* `httpcore2.UnsupportedProtocol`