The latest release, 2.1.0, is from 2022-01-26, and installing it on a current
Linux Python needs a workaround that master no longer needs.
Measured today on Ubuntu 24.04 / Python 3.11, two clean venvs, both with
setuptools 84.0.0, the only difference being the source:
pip install ear==2.1.0
ear-render --help -> exit 1
ModuleNotFoundError: No module named 'pkg_resources'
File ".../ear/core/bs2051.py", line 1, in
pip install git+https://github.com/ebu/ebu_adm_renderer@master
ear-render --help -> exit 0
bs2051.py imports pkg_resources at module level in 2.1.0; setuptools >= 81 no
longer ships it, so the entry point dies at import. On master pkg_resources is
gone entirely and importlib_resources is used instead. Separately, 2.1.0 still
installs through setup.py, which is the path that also trips Debian-patched
setuptools; master has moved to pyproject.toml.
So anyone installing the reference renderer from PyPI today still needs to pin
setuptools<81 in a venv, while master has needed neither workaround for some
time.
One small thing either way: pyproject.toml on master still carries
version = '2.1.0', the same string as the 2022 tag.
I am not reporting a defect --- both problems are already fixed in your tree.
This is only a note that the fixes are not reachable from a release, in case a
tag is cheaper than it looks.
The latest release, 2.1.0, is from 2022-01-26, and installing it on a current
Linux Python needs a workaround that master no longer needs.
Measured today on Ubuntu 24.04 / Python 3.11, two clean venvs, both with
setuptools 84.0.0, the only difference being the source:
pip install ear==2.1.0
ear-render --help -> exit 1
ModuleNotFoundError: No module named 'pkg_resources'
File ".../ear/core/bs2051.py", line 1, in
pip install git+https://github.com/ebu/ebu_adm_renderer@master
ear-render --help -> exit 0
bs2051.py imports pkg_resources at module level in 2.1.0; setuptools >= 81 no
longer ships it, so the entry point dies at import. On master pkg_resources is
gone entirely and importlib_resources is used instead. Separately, 2.1.0 still
installs through setup.py, which is the path that also trips Debian-patched
setuptools; master has moved to pyproject.toml.
So anyone installing the reference renderer from PyPI today still needs to pin
setuptools<81 in a venv, while master has needed neither workaround for some
time.
One small thing either way: pyproject.toml on master still carries
version = '2.1.0', the same string as the 2022 tag.
I am not reporting a defect --- both problems are already fixed in your tree.
This is only a note that the fixes are not reachable from a release, in case a
tag is cheaper than it looks.