python-lzf deprecation warning

[bnlawrence]

With the new lzw support we have a dependency in testing (and users will have in production) on python-lzw. Currently when building this gives a build warning:

 DEPRECATION: Building 'python-lzf' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future 
version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by 
setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the 
source tree of 'python-lzf'. Discussion can be found at https://github.com/pypa/pip/issues/6334

@valeriupredoi Is this something we need to do something about? Can we do something about it?

[valeriupredoi]

@bnlawrence I don't see this. How are you installing so you can get this?

[bmaranville]

Could switch to a maintained version, e.g. https://github.com/FledgeXu/python-neo-lzf (https://pypi.org/project/python-neo-lzf), though it's a pretty new fork without a lot of reputation yet. Is lzf not that popular among python users?

[valeriupredoi]

@bmaranville - no, worst case scenario, I take over the maintenance of that package - but like I said in the comment, we need to figure out how @bnlawrence is installing it since I don't get the deprecation warning when I do a bog standard pip install installation 🍺

[bnlawrence]

So I can repeat this by doing:

pip uninstall python-lzf
Found existing installation: python-lzf 0.2.6
Uninstalling python-lzf-0.2.6:
  Would remove:
    /Users/bnl28/mambaforge/envs/pyfive-25aug/lib/python3.12/site-packages/lzf.cpython-312-darwin.so
    /Users/bnl28/mambaforge/envs/pyfive-25aug/lib/python3.12/site-packages/python_lzf-0.2.6.dist-info/*
Proceed (Y/n)? y
  Successfully uninstalled python-lzf-0.2.6
pip install python-lzf --no-cache-dir
Collecting python-lzf
  Downloading python_lzf-0.2.6.tar.gz (9.8 kB)
  Preparing metadata (setup.py) ... done
Building wheels for collected packages: python-lzf
  DEPRECATION: Building 'python-lzf' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'python-lzf'. Discussion can be found at https://github.com/pypa/pip/issues/6334
  Building wheel for python-lzf (setup.py) ... done
  Created wheel for python-lzf: filename=python_lzf-0.2.6-cp312-cp312-macosx_11_0_arm64.whl size=6846 sha256=c18389bbae437c7c0f0067d61a22d58ed0b94853e1adb8d2a2ec684e342181f3
  Stored in directory: /private/var/folders/gq/txrkd1kn5zzfjr39ms_lmcxr0000gq/T/pip-ephem-wheel-cache-sqc_g02b/wheels/0c/9b/11/c1baf6f3e2841c29980d34aaee5f98ac97de91ef429c068ef4
Successfully built python-lzf
Installing collected packages: python-lzf
Successfully installed python-lzf-0.2.6

[valeriupredoi]

agh! I completely missed the --use-pep517 flag - I'll have a closer look at the python-lzf package, we may have to move that to ours, another option is to use the fork that @bmaranville pointed to, but I'd be weary of new forks that we don't know how actively developed they'll end up being