René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Requested lz4~=4.3 from file, but installing version 0.0.0/version: none","articleBody":"Trying to build a flatpak application from a Python project which requires lz4.\r\n\r\nHowever, when building from source, the build fails:\r\n```\r\n========================================================================\r\nBuilding module python3-lz4 in /home/evilsupahfly/src/Flatpak Testing/.flatpak-builder/build/python3-lz4-1\r\n========================================================================\r\nRunning: pip3 install --verbose --exists-action=i --no-index --find-links=\"file://${PWD}\" --prefix=${FLATPAK_DEST} \"lz4==4.3.3\" --no-build-isolation\r\nUsing pip 24.0 from /usr/lib/python3.11/site-packages/pip (python 3.11)\r\nLooking in links: file:///run/build/python3-lz4\r\nERROR: Could not find a version that satisfies the requirement lz4==4.3.3 (from versions: none)\r\nERROR: No matching distribution found for lz4==4.3.3\r\nError: module python3-lz4: Child process exited with code 1\r\n```\r\n\r\nAccording to the help I got from my original [help request](https://discuss.python.org/t/requested-lz4-4-3-from-file-but-installing-version-0-0-0/57581/5) on python.org, this is a bug in lz4 itself:\r\n\r\n\u003e As can be seen on GitHub, the pyproject.toml file doesn’t specify a version number. pyproject.toml is in fact quite minimal in this case; it’s only specifying some build dependencies, and expecting the setup.py process to create all the needed metadata.\r\n\u003e \r\n\u003e But this project wants to compute the version using setuptools-scm, an [extension to setuptools that](https://pypi.org/project/setuptools-scm/) checks version control to retrieve information about the project and compute things like the version number.\r\n\u003e \r\n\u003e More specifically, it’s configured to use setuptools-scm to write a version number into a lz4/version.py file in the source directory, and then use that during building to set the version for metadata. (The file is then also available for the program to use internally at runtime.) The GitHub repository doesn’t contain this file (version control wouldn’t be tracking it on the devs’ machine) and neither does the source tarball. This is a problem, because it prevents anyone else from building from the source tarball - when unpacked on someone else’s machine, there’s no Git repo from which to extract the version info.\r\n\u003e \r\n\u003e So when the package is built from the sdist, it can’t produce the necessary file, therefore can’t inform the metadata creation process, and therefore falls back to a default version number.\r\n\r\nSo when attempting to build from source, it fails because the metadata doesn't contain any useable version information.","author":{"url":"https://github.com/EvilSupahFly","@type":"Person","name":"EvilSupahFly"},"datePublished":"2024-07-08T15:49:57.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/280/python-lz4/issues/280"}