Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
A clean pip install modern-treasury in a fresh venv (python 3.13), then modern_treasury.ModernTreasury([credential]: [redacted] organization_id='456'), crashed on client init — the traceback ran through _client.py into httpx internals. The httpx dependency wasn't pinned, so a new httpx release broke the SDK. Version 1.43.1 was supposed to contain the fix but hadn't published to PyPI (the publish had failed).
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Two things went wrong: an unpinned httpx broke client construction, and the fixed release (1.43.1) failed to publish to PyPI. Workaround confirmed by the maintainer: pip install httpx<0.28, or install the SDK straight from GitHub. The real fix shipped in v1.44.0 — the reporter confirmed 1.44.0 is picked up by default and contains the fix. Source: https://github.com/Modern-Treasury/modern-treasury-python/issues/570
Shows how to fix modern-treasury python SDK broken on fresh install: httpx dependency not pinned (1.43.x). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Walks through set custom httpx connection pool limits in modern-treasury python SDK, step by step.
Shows how to fix importError: cannot import name 'ModelField' from 'pydantic.fields' with modern-treasury python SDK. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.