New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/issues/46545#issuecomment-1757540425

Comment:
Unfortunately, `python3-Levenshtein` is kind of a mess. Updating fully is ugly because it depends a new RapidFuzz package, and both of those depend on scikit-build, which 1) I suspect would require some hacking to work with our cross-compilation setup; and 2) the authors of scikit-build already seem to be deprecating it in favor of another variant. I considered patching the version we have to work around the Levenshtein problem, but that is a non-trivial patch that requires some thought about Python object lifetimes in C extensions. Because I don't actually use this software, I don't know anything about Levenshtein and am not sure what the right approach is there. Finally, I considered updating to a newer (but still outdated) Levenshtein, which uses Cython without CMake and scikit-build. The newer version probably avoids our issues, but still depends on RapidFuzz and may or may not require scikit-build anyway. I haven't looked very closely at this option.

For now, a workaround seems to be shadoing the Levenshtein package in a virtual environment:

```sh
python3 -m venv --system-site-packages ${HOME}/ulauncher.venv
${HOME}/ulauncher.venv/bin/pip install -U Levenshtein
```

Whenever you want to run `ulauncher`, run it as

```sh
${HOME}/ulauncher.venv/bin/python3 /usr/bin/ulauncher
```

instead. This will at least bring up the program for me, but I can't test it any more thoroughly. You can, of course, put the venv anywhere you like.