uv pip compile fails to build pylzma dependency

[carno]

As far as I understand this is more of a pylzma issue, but as it works with pip-compile I will leave it here in case it's something worth a workaround aka "correction for a common mistake" as mentioned in #1528 (comment)

If I'm not mistaken, the culprit is in how pylzma generates it's version when being built locally: https://github.com/fancycode/pylzma/blob/master/version.py

As I run uv pip compile in Docker, in a gitlab runner, it adds hash of my repository to the version string (at least the part after -g matches that)…

$ uv --version
uv 0.1.5
$ uv pip compile --output-file=- images/common/requirements.in
error: Failed to download and build: pylzma==0.5.0
  Caused by: Failed to build: pylzma==0.5.0
  Caused by: Build backend failed to determine extra requires with `build_wheel()`:
--- stdout:
--- stderr:
Traceback (most recent call last):
  File "<string>", line 10, in <module>
  File "/builds/redacted/.cache/uv/.tmpHEBm3b/.venv/lib/python3.11/site-packages/setuptools/build_meta.py", line 325, in get_requires_for_build_wheel
    return self._get_build_requires(config_settings, requirements=['wheel'])
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/builds/redacted/.cache/uv/.tmpHEBm3b/.venv/lib/python3.11/site-packages/setuptools/build_meta.py", line 295, in _get_build_requires
    self.run_setup()
  File "/builds/redacted/.cache/uv/.tmpHEBm3b/.venv/lib/python3.11/site-packages/setuptools/build_meta.py", line 480, in run_setup
    super().run_setup(setup_script=setup_script)
  File "/builds/redacted/.cache/uv/.tmpHEBm3b/.venv/lib/python3.11/site-packages/setuptools/build_meta.py", line 311, in run_setup
    exec(code, locals())
  File "<string>", line 189, in <module>
  File "/builds/redacted/.cache/uv/.tmpHEBm3b/.venv/lib/python3.11/site-packages/setuptools/__init__.py", line 103, in setup
    return distutils.core.setup(**attrs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/builds/redacted/.cache/uv/.tmpHEBm3b/.venv/lib/python3.11/site-packages/setuptools/_distutils/core.py", line 147, in setup
    _setup_distribution = dist = klass(attrs)
                                 ^^^^^^^^^^^^
  File "/builds/redacted/.cache/uv/.tmpHEBm3b/.venv/lib/python3.11/site-packages/setuptools/dist.py", line 314, in __init__
    self.metadata.version = self._normalize_version(self.metadata.version)
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/builds/redacted/.cache/uv/.tmpHEBm3b/.venv/lib/python3.11/site-packages/setuptools/dist.py", line 350, in _normalize_version
    normalized = str(Version(version))
                     ^^^^^^^^^^^^^^^^
  File "/builds/redacted/.cache/uv/.tmpHEBm3b/.venv/lib/python3.11/site-packages/setuptools/_vendor/packaging/version.py", line 198, in __init__
    raise InvalidVersion(f"Invalid version: '{version}'")
setuptools.extern.packaging.version.InvalidVersion: Invalid version: '15.0.0-744-gb2d6'

[charliermarsh]

My guess is that pip does the build in a temporary directory outside of the project hierarchy, whereas we're doing it within a temporary directory in the .venv?

[charliermarsh]

I consider this a bug though. I've seen it in other packages too.

[charliermarsh]

Fixed in #1782.