From: dom0 <dom0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Ulauncher broken after python 3.12 upgrade
Date: Wed, 11 Oct 2023 18:14:15 +0200 [thread overview]
Message-ID: <20231011161415.Lw7foBwm9_67OPn0Hj0jhsWDTSaS_NTEjaWMzFJ_Pv8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46545@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2034 bytes --]
New comment by dom0 on void-packages repository
https://github.com/void-linux/void-packages/issues/46545#issuecomment-1758042016
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:
>
> ```shell
> 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
>
> ```shell
> ${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.
Thanks for the feedback and help. I tried the same workarounds before opening issue and in the end I opted to switch to wofi. "It's a Python Thing :)"
For those who are looking for an alternative, below are the wofi options that I am using to have similar behavior (not feature complete) to ulauncher:
`wofi -n -i --show drun --allow-images --allow-markup --matching=fuzzy`
next prev parent reply other threads:[~2023-10-11 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 5:47 [ISSUE] " dom0
2023-10-10 8:56 ` icp1994
2023-10-11 12:01 ` ahesford
2023-10-11 12:01 ` ahesford
2023-10-11 16:14 ` dom0 [this message]
2023-11-23 4:44 ` [ISSUE] [CLOSED] " abenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231011161415.Lw7foBwm9_67OPn0Hj0jhsWDTSaS_NTEjaWMzFJ_Pv8@z \
--to=dom0@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).