Repository navigation
Add support for -dev for PyPy and other interpreters #508
Description
In #213 (comment)_, Ivan suggested that instead of providing support for pre-release versions, users should expect to append -dev to every version. Unfortunately, if one attempts to append -dev to a PyPy version, the action fails with the error:
Invalid 'version' property for PyPy. Both Python version and PyPy versions should satisfy SemVer notation. See README for examples and documentation.
This error is confusing because it suggests that -dev isn't allowed for either (C)Python or PyPy, when in fact appending -dev is the recommended workaround to the behavior that emergent versions of Python are invisible without it on CPython.
In any case, this issue is primarily a feature request to bring PyPy (and any future interpreters) to parity with CPython with -dev support so that -dev doesn't have to be specified in each and every version and pollute the version number in the matrix.
Activity
Add PyPy to the test matrix on Linux. Fixes #63.
vsafonkin commentedon Sep 26, 2022
Hi @jaraco, we will take a look at this, thanks.
mattip commentedon Nov 22, 2022
Hi. PyPy dev here. The list of available pypy versions comes from this file which is managed from the PyPy repo. Would you like the
-devversion to be an alias for thenightlyPyPy builds? That would be pretty easy to add to theversions.jsonfile.Add PyPy to the test matrix on Linux. Fixes jaraco/skeleton#63.
Replace workaround for actions/setup-python#508 with 'allow-prereleases'
pypi-tempora: Autospec creation for update from version 5.3.0 to vers…
pypi-jaraco.functools: Autospec creation for update from version 3.7.…
pypi-keyring: Autospec creation for update from version 24.1.0 to ver…
pypi-jaraco.collections: Autospec creation for update from version 4.…
pypi-portend: Autospec creation for update from version 3.1.0 to vers…
pypi-inflect: Autospec creation for update from version 6.0.4 to vers…
python3-importlib-metadata: upgrade 6.7.0 -> 6.8.0
10 remaining items
python3-importlib-metadata: upgrade 6.7.0 -> 6.8.0
python3-importlib-metadata: upgrade 6.7.0 -> 6.8.0
python3-importlib-metadata: upgrade 6.7.0 -> 6.8.0
python3-importlib-metadata: upgrade 6.7.0 -> 6.8.0
python3-importlib-metadata: upgrade 6.7.0 -> 6.8.0
python3-importlib-metadata: upgrade 6.7.0 -> 6.8.0
python3-importlib-metadata: upgrade 6.7.0 -> 6.8.0
python3-importlib-metadata: upgrade 6.7.0 -> 6.8.0
python3-importlib-metadata: upgrade 6.7.0 -> 6.8.0
dmitry-shibanov commentedon Jul 18, 2023
Hello @jaraco. I think it is not necessary to add support for dev because it changes version from
3.8-devto~3.8.0-0. For PyPy you can achieve the similar behaviour by specifying allow-prerelease.For now I'm going to close the feature request. if you have any concerns feel free to ping us.
pypi-setuptools: Autospec creation for update from version 68.0.0 to …
pypi-jaraco.text: Autospec creation for update from version 3.11.1 to…
pypi-jaraco.context: Autospec creation for update from version 4.3.0 …
Replace workaround for actions/setup-python#508 with 'allow-prereleases'