Skip to content

Commit 983aa7d

Browse files
committed
Update development status.
pyfuse3 (with Trio) is a critical dependency of S3QL, which I have started maintaining again. This means pyfuse3 will receive enough attention from me to keep it functional and tested.
1 parent 942278d commit 983aa7d

File tree

1 file changed

+7
-12
lines changed

1 file changed

+7
-12
lines changed

README.rst

Lines changed: 7 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,7 @@
11
..
22
NOTE: We cannot use sophisticated ReST syntax (like
33
e.g. :file:`foo`) here because this isn't rendered correctly
4-
by PyPi and/or BitBucket.
5-
6-
7-
Warning - no longer developed!
8-
==============================
9-
10-
pyfuse3 is no longer actively developed and just receiving community-contributed
11-
maintenance to keep it alive for some time.
4+
by PyPi.
125
136

147
The pyfuse3 Module
@@ -36,11 +29,13 @@ questions, please use the general `FUSE mailing list`_. A searchable
3629
Development Status
3730
------------------
3831

39-
pyfuse3 is in beta. Bugs are likely.
32+
pyfuse3 is stable when used with Trio. The current maintainers ensure that bugs
33+
are addressed and pyfuse3 continues to work with new Python and libfuse
34+
versions. There is no plan to add new features or other non-bugfix work.
35+
However, pull requests for new features or other improvements may be accepted.
4036

41-
pyfuse3 uses semantic versioning. This means backwards incompatible
42-
changes in the API will be reflected in an increase of the major
43-
version number.
37+
Using pyfuse3 with asyncio (rather than Trio) support is less well tested,
38+
there may be bugs, and some of them may not be easily fixable.
4439

4540

4641
Contributing

0 commit comments

Comments
 (0)