How to set custom httpx connection pool limits in modern-treasury python SDK

TL;DR

A maintainer later confirmed version 1.10 resolved the issue.

Steps

1. Before 1.10 there was no public option , the documented workaround was to replace the internal HTTP client: build custom_client = httpx.Client(base_url=standard_client.base_url, timeout=standard_client._timeout, headers=standard_client.headers, limits=httpx.Limits(max_connections=120, max_keepalive_connections=100, keepalive_expiry=20)) and assign it to modern_treasury._client. A maintainer confirmed version 1.10 resolved the issue, so upgrade and use whatever pool options the new release exposes. Source: https://github.com/Modern-Treasury/modern-treasury-python/issues/72

Expected: A maintainer confirmed version 1.10 resolved the issue, so upgrade and use whatever pool options the new release exposes.

When to use

You are seeing this: The modern-treasury python SDK didn't expose httpx's limits kwarg for tuning the connection pool (max connections, keepalive). Use this skill when you run into "How to set custom httpx connection pool limits in modern-treasury python SDK".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 1.10. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/Modern-Treasury/modern-treasury-python/issues/72

In the thread https://vectle.com/threads/thrIYuJlCqd5e1qMe2--sRm1w, the question was: The modern-treasury python SDK didn't expose httpx's limits kwarg for tuning the connection pool (max connections, keepalive). A user posted a workaround that reaches into `moderntreasury.client, builds a new httpx.Client` copying baseurl/timeout/headers and passing httpx.Limits(max_connections=120, max_keepalive_connections=100, keepalive_expiry=20), then swaps it back onto the client. A maintainer later confirmed version 1.10 resolved the issue. The verified resolution was: Before 1.10 there was no public option , the documented workaround was to replace the internal HTTP client: build custom_client = httpx.Client(base_url=standard_client.base_url, timeout=standard_client._timeout, headers=standard_client.headers, limits=httpx.Limits(max_connections=120, max_keepalive_connections=100, keepalive_expiry=20)) and assign it to modern_treasury._client. A maintainer confirmed version 1.10 resolved the issue, so upgrade and use whatever pool options the new release exposes. Source: https://github.com/Modern-Treasury/modern-treasury-python/issues/72