Arch Linux

Description:
Although the fuse situation in the python ecosystem is rather confusing and somewhat dire there is a switch possible.
Is the switch needed? Probably not really. It depends more on viewpoints and arguments?

Arch's borg package has a optdepend on python-llfuse which allows the use of borg mount. This dependency is only compatible with libfuse2 (aka fuse2) and is deprecated[0]. Although there may be releases to make it work with current python versions[1].

Borg upstream itself is more in favour of pyfuse3[2]
Quote: "optionally, if you wish to mount an archive as a FUSE filesystem, you need a FUSE implementation for Python:
Either pyfuse3_ (preferably, newer and maintained) or llfuse_ (older, unmaintained now). See also the BORG_FUSE_IMPL env variable."
Although they still make the use of llfuse possible.
What is the main benefit of pyfuse3? Uses the maintained libfuse3. But there is also this[4]. But like with llfuse, there was recently a release.

To summarize:
The main benefit would be to reduce packages using fuse2 by one.
But one cannot hide that the replacement itself is also somewhat questionable.
The replacement would require the adoption/promotion of an aur package. Although on the other hand python-llfuse could be dropped to the AUR, as it is only used by borg. (The optdep on borgmatic is somewhat misleading, as borg does the lifting).
Dunno what is the best call as everything is a mixed bag, but I thought it might be worth bringing this to attention.
_____________
[0] https://github.com/python-llfuse/python-llfuse/blob/master/README.rst#the-python-llfuse-module
[1] https://github.com/python-llfuse/python-llfuse/blob/release-1.4.4/Changes.rst#release-144-2023-05-21
[2] https://github.com/borgbackup/borg/blob/1.2.4/docs/installation.rst#dependencies
[3] https://aur.archlinux.org/packages/python-pyfuse3
[4] https://github.com/libfuse/pyfuse3#warning---no-longer-developed