acsr
(acsr)
March 18, 2025, 3:46pm
1
The Installation
instructions for GitHub - zestsoftware/zest.releaser: Python software releasing made easy and repeatable are only mentioning pip
or buildout
based installations.
Whether or not using an venv is not covered explicitly.
There is an option to install a recommended
extra that you can get by installing zest.releaser[recommended]
instead of zest.releaser
.
when I try to install:
uv tool install zest.releaser[recommended]
I get: no matches found: zest.releaser[recommended]
Is it sufficient to just using uvx --from zest-releaser <EXECUTABLE_NAME>
instead?
I am jumpoing in into the use of zest.releaser and did not find this covered in the docs or in the forum.
The search at https://zestreleaser.readthedocs.io/ is broken for me with an:
500 Internal Server Error | nginx
acsr
(acsr)
March 18, 2025, 3:56pm
2
using uv tool install zest.releaser
works (without the [recommended]
option) resulting in output (including wheel
, readme-renderer
; but not check-manifest
, pyroma
):
Resolved 31 packages in 403ms
Installed 31 packages in 52ms
+ build==1.2.2.post1
+ certifi==2025.1.31
+ cffi==1.17.1
+ charset-normalizer==3.4.1
+ cmarkgfm==2024.11.20
+ colorama==0.4.6
+ docutils==0.21.2
+ id==1.5.0
+ idna==3.10
+ jaraco-classes==3.4.0
+ jaraco-context==6.0.1
+ jaraco-functools==4.1.0
+ keyring==25.6.0
+ markdown-it-py==3.0.0
+ mdurl==0.1.2
+ more-itertools==10.6.0
+ nh3==0.2.21
+ packaging==24.2
+ pycparser==2.22
+ pygments==2.19.1
+ pyproject-hooks==1.2.0
+ readme-renderer==44.0
+ requests==2.32.3
+ requests-toolbelt==1.0.0
+ rfc3986==2.0.0
+ rich==13.9.4
+ setuptools==76.1.0
+ twine==6.1.0
+ urllib3==2.3.0
+ wheel==0.45.1
+ zest-releaser==9.5.0
Installed 9 executables: addchangelogentry, bumpversion, fullrelease, lasttagdiff, lasttaglog, longtest, postrelease, prerelease, release
Executables are working!
You had the name of the package incorrect, and you need to double quote packages with dependency groups. Read on.
I do this for plone-sphinx-theme .
"sphinx-sitemap>=2.6.0",
"sphinx-theme-builder[cli]>=0.2.0b2",
"sphinx-tippy>=0.4.3",
"sphinxcontrib-httpdomain>=1.8.1",
"sphinxcontrib-httpexample>=1.3",
"sphinxcontrib-mermaid>=1.0.0",
"sphinxcontrib-video>=0.4.1",
"sphinxcontrib-youtube>=1.4.1",
"sphinxext-opengraph>=0.9.1",
"vale>=3.9.5.0",
"zest-releaser[recommended]>=9.4.0",
"zestreleaser-towncrier>=1.3.0",
]
[project.entry-points]
"sphinx.html_themes" = { plone_sphinx_theme = "plone_sphinx_theme" }
[project.urls]
Repository = "https://github.com/plone/plone-sphinx-theme"
Documentation = "https://plone-sphinx-theme.readthedocs.io/"
You can add a development dependency to your pyproject.toml
with uv .
uv add --dev "zest-releaser[recommended]"
uv will pin a compatible version. So nice!
I use a Makefile to abstract the uv commands into specific tasks, because trying to remember the syntax or sequence of commands leads my brain to a buffer overflow error.
2 Likes
acsr
(acsr)
March 21, 2025, 8:06pm
4
the text "uvx --from zest-releaser <EXECUTABLE_NAME>" was just copied from a note from an error response in the terminal. The same command without
executable name worked. Not sure if I actually mistyped it or it was the insane rename packages issue we were confronted with.