Repository navigation
Wondering if I can rely on python library #1842
|
Hi, I was wondering if the python lib is planned to be supported long term or if I should switch to using docker images? Ideally I would be able to upgrade versions easily which was why I didn't fork |
Replies: 2 comments
|
The Docker is updated more regularly. Better to use it. |
|
The package is maintained and no longer lags. Releases now build the wheel and the Docker images as parallel jobs in a single workflow from the same commit and version, and a missing PyPI publish raises a warning on the release rather than passing silently. PyPI currently serves 0.45.0, matching the repository, and every release from 0.40.0 onwards is present; the gap you ran into in 2025 was a publishing outage that has since been fixed. So installing from PyPI and pinning a version is a reasonable way to keep upgrading without forking. The caveat is that there is no declared public Python API: the package exports nothing from its root, the only supported entry point is the |
The package is maintained and no longer lags. Releases now build the wheel and the Docker images as parallel jobs in a single workflow from the same commit and version, and a missing PyPI publish raises a warning on the release rather than passing silently. PyPI currently serves 0.45.0, matching the repository, and every release from 0.40.0 onwards is present; the gap you ran into in 2025 was a publishing outage that has since been fixed. So installing from PyPI and pinning a version is a reasonable way to keep upgrading without forking. The caveat is that there is no declared public Python API: the package exports nothing from its root, the only supported entry point is the
pr-agentcons…