-
-
Notifications
You must be signed in to change notification settings - Fork 30
Installation fails due to PyO3 dependency - incompatible with Python 3.13 #16
Comments
Also encountering this issue, including when uninstalling from brew and reinstalling via pipx. From what I can tell online, version 0.22 of PyO3 fixes it, but I'm not sure where that version gets specified. |
also running into this with homebrew and pipx. workaround i'm using is to use llm via uvx uvx --python 3.12 llm install llm-claude-3
# for some reason ANTHROPIC_API_KEY wasn't being picked up
uvx --python 3.12 llm keys set claude --value "$ANTHROPIC_API_KEY" i saved this as an alias in fish: alias --save llm "uvx --python 3.12 llm" |
I just had a long chat with Claude about this.
|
I just hit this one too, in CI: https://github.com/simonw/llm-claude-3/actions/runs/11565609702/job/32192886633
|
Here's the issue for the PyO3 Python 3.13 compatibility: And this PR tracking what needs to be done, which says it's aiming for a November 1st release at the moment: |
Filed an issue against anthropic here: Since the PyO3 fix is due within a week I'm going to leave this for the moment. |
I opened a PR against the Anthropic client library here: |
Here's a workaround using my Anthropic client library branch. First install my branch that works in Python 3.13: llm install https://github.com/simonw/anthropic-sdk-python/archive/9c13bb441ee4eb88a100ed363fc431ec8fd30c43.zip Now this should work: llm install llm-claude-3 |
Docker is a handy tool for working around odd environment install issues, and is what I reached for to work around this particular problem. I don't see anything docker-specific in the issues, so posting my solution here in case it helps anyone else :) Dockerfile:
I created a basic alias in
Also just wanted to say thanks for making a very nice CLI for this, I use it all the time. |
I just did a fresh installation of
llm
via brew on a M1 Mac, followed byllm install llm-claude-3
.Here, I get the following error
Any ideas on that? Was there maybe a recent update to [email protected]? The suggested workaround
PYO3_USE_ABI3_FORWARD_COMPATIBILITY=1
also did not work out.The text was updated successfully, but these errors were encountered: