The atproto==0.0.54 package has a dependency on httpx with version >=0.25.0, <0.27.0. When httpx==0.28.1 (or any version outside this range) is also required, a dependency conflict arises, preventing successful installation of the project’s requirements. This is a common issue when deploying applications with these dependencies, such as on platforms like Streamlit.
Expected Behavior
The package installer should be able to resolve the dependencies and install all required packages without conflict, or at least provide a clearer error message suggesting possible resolutions.
Details
Python version: 3.12
Package installers affected: pip, uv, and others.
Operating system: The specific OS doesn’t seem to be the root cause, but it has been observed on Streamlit’s deployment environment, which is likely Linux-based.
Additional Context
This dependency conflict prevents applications relying on both atproto==0.0.54 and potentially newer features/versions of httpx from being deployed successfully.
It would be beneficial if atproto could either update its httpx dependency range or provide clearer guidance on how to handle this conflict.
A conflict means that there is no set of packages that fulfills all the requirements. There is nothing a package manager can do about that.
This is what uv says:
× No solution found when resolving dependencies:
╰─▶ Because atproto==0.0.54 depends on httpx>=0.25.0,<0.27.0 and you require
atproto==0.0.54, we can conclude that you require httpx>=0.25.0,<0.27.0.
And because you require httpx==0.28.1, we can conclude that your
requirements are unsatisfiable.
And pip:
ERROR: Cannot install -r /mount/src/atproto_httpx/requirements.txt (line 1) and httpx==0.28.1 because these package versions have conflicting dependencies.
The conflict is caused by:
The user requested httpx==0.28.1
atproto 0.0.54 depends on httpx<0.27.0 and >=0.25.0
To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict
I wouldn’t know how to make it clearer, and your own description of the issue is pretty much the same.
They already did, but unfortunately they are still lagging behind. I suspect there may be good reasons for it, but I don’t know what they can be. Maybe incompatible changes in 0.28 that are hard to deal with. Hopefully they will tell you.
There is no handling. atproto==0.0.54 requires httpx>=0.25.0,<0.27.0, that’s all. Installing atproto==0.0.54 and httpx>=0.28.1 in the same environment is not possible.
Thanks for stopping by! We use cookies to help us understand how you interact with our website.
By clicking “Accept all”, you consent to our use of cookies. For more information, please see our privacy policy.
Cookie settings
Strictly necessary cookies
These cookies are necessary for the website to function and cannot be switched off. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms.
Performance cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us understand how visitors move around the site and which pages are most frequently visited.
Functional cookies
These cookies are used to record your choices and settings, maintain your preferences over time and recognize you when you return to our website. These cookies help us to personalize our content for you and remember your preferences.
Targeting cookies
These cookies may be deployed to our site by our advertising partners to build a profile of your interest and provide you with content that is relevant to you, including showing you relevant ads on other websites.