pleiszenburg / refuse Goto Github PK

View Code? Open in Web Editor NEW

This project forked from fusepy/fusepy

60.0 60.0 11.0 426 KB

Simple cross-plattform ctypes bindings for libfuse / FUSE for macOS / WinFsp

License: ISC License

Python 97.92% C 0.49% Makefile 1.59%

bindings filesystems fuse libfuse python

refuse's People

Contributors

Stargazers

Watchers

Forkers

n-coder suprasummus cdanis emre5544 clach04 wolfdwyc yoilyl cdrini mattccs yarikoptic

refuse's Issues

How to use it with Windows?

Congrats for this nice project!

Can you give an example of how to use it with Windows? (which dependencies / libraries to install first)

PS: If possible, without cygwin, and without having to install WinFSP. Is libfuse available directly for Windows?

fusepy#97: broken exception handling

Tracking fusepy#97.

fusepy#57: Does this support using the dokany fuse wrapper for use on Windows?

Tracking fusepy#57

Support CAP_CASE_INSENSITIVE, advertising a file system as case-insensitive

Taken from #6.

PR fusepy#101

Tracking fusepy#101, variation of fusepy#67

Support init options and parameters

fusepy#81: Irritating default behavior of Operations class - raising FuseOSError(EROFS) where it really should not

Tracking fusepy#81

@billziss-gh Please correct me if I am wrong: All relevant changes to fuse.py and fusell.py for Windows and Cygwin support were merged into fusepy through fusepy#110 and fusepy#107? I have been going back and forth through diff's of fusepy's head and your fork's head, but I could not spot any other relevant difference.

Is the beast alive?

It seems that lots of progress was done on top of the original fusepy but no recent activity/fixes, and some forks have fixes on top.

I would appreciate if someone updates on the status of the project or mentions any alternative.

Cheers!

fusepy#28: Implement read_buf() and write_buf()

Tracking fusepy#28

self used in staticmethod

refuse/src/refuse/high.py

Line 888 in 0fb0df4

self.__critical_exception = e

PR fusepy#125

Tracking fusepy#125

This pull request introduces Open BSD support.

Missing UTIME_OMIT and UTIME_NOW

Patched in high level API, missing in low level API.

Support FSP_FUSE_CAP_READDIR_PLUS, WinFsp's "enhanced" readdir

Taken from #6.

PR fusepy#130

Tracking fusepy#130.

A type error here might be intentional. Not (yet) merging.

kick-off

Continuing fusepy#134.

“nothreads” argument explanation

I've been fiddling for a bit with the fusepy package with python3.

When trying to create a FUSE instance, I came across the nothreads argument.

Can anyone please elaborate on what this does?

I can guess that setting this flag to True the software no longer supports multithreading, but what I would like to know is how it changes the software's behaviour, what would the flow be with and without setting it to True?

P.S. - I know that this is a fork of fusepy, but unfortunately, I didn't get any answers there

Thanks