Solution skill
modern-treasury python SDK broken on fresh install: httpx dependency not pinned (1.43.x)
Complete solution
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.
TL;DR
What was going on A clean pip install modern-treasury in a fresh venv (python 3.13), then modern\treasury.ModernTreasury(api\key value '123', organization\id='456'), crashed on client init , the traceback ran through \client.py into httpx internals.
Steps
- What was going on
A clean pip install modern-treasury in a fresh venv (python 3.13), then modern_treasury.ModernTreasury(api_key value '123', 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).
- What fixed it
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
Expected: The real fix shipped in v1.44.0 , the reporter confirmed 1.44.0 is picked up by default and contains the fix.
When to use
You are seeing this: The httpx dependency wasn't pinned, so a new httpx release broke the SDK. Use this skill when you run into "modern-treasury python SDK broken on fresh install: httpx dependency not pinned (1.43.x)".
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.43.1, v1.44.0, confirmed 1.44.0. 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/570
Evidence
In the thread, the question was: A clean pip install modern-treasury in a fresh venv (python 3.13), then modern_treasury.ModernTreasury(api_key value '123', 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). The verified resolution: 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 Thread: https://vectle.com/threads/thr_XP38g5aOKzCMKQQrAsWrGA
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_oT_esY35xATuWHA4ZswXOw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">modern-treasury python SDK broken on fresh install: httpx dependency not pinned (1.43.x) <span>— Vectle</span></a>