New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Version normalization making an unexpected change #4239
Comments
I guess what is happening is:
(Or vice-versa) To read more about build isolation you can refer to https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/#build-isolation. To consistently disable the "build isolation" feature in pip you can:
If you try this you should at least see a consistent behaviour between the local machine and CI. Would you like to give this a try and see how it goes? |
I am supposing that here you mean |
Thank you @abravalheri I will try that.
Ah yes, I did mean |
Alternatively, to consistently enable build isolation, you can add a [build-system]
requires = ["setuptools>=69.1.1"]
build-backend = "setuptools.build_meta" This way, you can specify a minimum version required for the setuptools that will be installed in the "disposable" build environment. |
setuptools version
>=40.8.1
Python version
3.11
OS
ubuntu
Additional environment information
Run in the github action
Description
When building a wheel using github actions, my version was normalized from
24.2.25r0
to24.2.25.post0
. I am not able to reproduce this locally, as24.2.25r0
should be a valid version name. Here is a link the the action logs: https://github.com/Pioreactor/pioreactor/actions/runs/8040467416/job/21958604300#step:5:10Expected behavior
I expected there to be no change to the version name.
How to Reproduce
I've rerun the github action, and it's giving the same change.
However, locally, no change is introduced:
Output
'24.2.25rc0'
The text was updated successfully, but these errors were encountered: