From: Nikolaus Rath <Nikolaus@rath.org>
To: fuse-devel@lists.linux.dev, fuse-devel@lists.sourceforge.net
Subject: [ANNOUNCE] pyfuse 3.5.0 has been released
Date: Wed, 13 May 2026 16:46:04 +0100 [thread overview]
Message-ID: <87bjejtirn.fsf@rath.org> (raw)
Dear all,
I'm happy to announce a new release of pyfuse3, version 3.5.0.
pyfuse3 is a set of Python 3 bindings for libfuse 3. It provides an
asynchronous API compatible with Trio and asyncio, and enables you to easily
write a full-featured Linux filesystem in Python.
From the changelog:
* Filesystems may now define a `~Operations.poll` method to support the ``epoll`` and `select`
system calls.
* The `FileHandleT` and `InodeT` types are no longer declared as *NewTypes* but are now simply
aliases for *int*. This should make it easier to write type annotations.
* Future releases of pyfuse will be signed with signify rather than GPG. The public key to verify
the signature of a the next version will always be included in the previous versions, so this
version already ships the public key that will be used to sign the next versions,
`signify/pyfuse-3.5.pub` for any bugfix releases and `signify/pyfuse-next.pub` for the
next minor (or major) release.
The following people have contributed code to this release:
Christopher Obbard <christopher.obbard@linaro.org>
Nikolaus Rath <Nikolaus@rath.org>
TW <tw@waldmann-edv.de>
Yaroslav Halchenko <debian@onerussian.com>
As usual, the newest release can be downloaded from PyPi at
https://pypi.python.org/pypi/pyfuse3/.
Please report any bugs on the issue tracker at
https://github.com/libfuse/pyfuse3/issues. For discussion and questions, please
use the general FUSE mailing list (i.e., this list) or the GitHub discussion
forum at https://github.com/libfuse/pyfuse3/discussions.
Best,
-Nikolaus
reply other threads:[~2026-05-13 15:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87bjejtirn.fsf@rath.org \
--to=nikolaus@rath.org \
--cc=fuse-devel@lists.linux.dev \
--cc=fuse-devel@lists.sourceforge.net \
/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