-
Notifications
You must be signed in to change notification settings - Fork 271
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
Build broken with setuptools v66 #571
Comments
To work around this issue, should I change |
Nixpkgs commit 451c632 upgraded setuptools from version 65.0.3 to version 67.4.0. This upgrade introduced a breaking change in setuptools [1] which causes the Sapling package's build to fail: setuptools.extern.packaging.version.InvalidVersion: Invalid version: '0.2.20230124-180750-hf8cd450a' This is an upstream issue [2]. For now, work around this issue in Nixpkgs by truncating Sapling's version number. Before 451c632: $ nix-env -q sapling sapling-0.2.20230228-144002-h9440b05e $ sl --version Sapling 0.2.20230228-144002-h9440b05e After this patch: $ nix-env -q sapling sapling-0.2.20230228-144002-h9440b05e $ sl --version Sapling 0.2.20230228 Refs: 451c632 [1] https://github.com/pypa/setuptools/blob/be6c0218bcba78dbd4ea0b5a8bb9acd5d5306240/CHANGES.rst#v6600 [2] facebook/sapling#571
Hi @strager thanks the posting the issue and fixing the NixOS build.
This looks good. We don't have plan to make the version number compatible with PEP 440, since Sapling is not a Python dependency in the Python eco-system. In the longer term, we may want to remove the |
Should be fixed by #606 |
Python setuptools version 66 dropped support for wacky version numbers: https://github.com/pypa/setuptools/blob/be6c0218bcba78dbd4ea0b5a8bb9acd5d5306240/CHANGES.rst#v6600
Sapling uses a version number like "0.2.20230124-180750-hf8cd450a", which is not compatible with setuptools v66. I get this error when building Sapling with setuptools v67.4.0:
The text was updated successfully, but these errors were encountered: