I'm trying to run multiple FUSE mounts from the same process - only the last call to pyfuse3.init() takes effect. Here's an example adapted from hello_asyncio.py:
It seems to me that the globals in pyfuse3.pyx are responsible for this behaviour. A quick-and-dirty fix would be to add to each function using the globals an optional context argument taking a dict of no-longer-global values. The entire init-run-close functionality could also be made part of the Operations class, but I'm not sure whether that is possible in a reasonably backwards compatible way.
I'm not super familiar with FUSE, and definitely unfamiliar with trio - would it nevertheless make sense for me to throw together a pull request, considering the lack of maintainers here?
Hi,
I'm trying to run multiple FUSE mounts from the same process - only the last call to pyfuse3.init() takes effect. Here's an example adapted from hello_asyncio.py:
Code from hello_asyncio.py
``` ''' hello_asyncio.py - Example file system for pyfuse3 using asyncio. This program presents a static file system containing a single file. Copyright © 2015 Nikolaus RathIt seems to me that the globals in pyfuse3.pyx are responsible for this behaviour. A quick-and-dirty fix would be to add to each function using the globals an optional context argument taking a dict of no-longer-global values. The entire init-run-close functionality could also be made part of the Operations class, but I'm not sure whether that is possible in a reasonably backwards compatible way.
I'm not super familiar with FUSE, and definitely unfamiliar with trio - would it nevertheless make sense for me to throw together a pull request, considering the lack of maintainers here?