Module name clash with python-fuse

[satta]

Just wanted to let you know that the name of the fusepy module to import, fuse, clashes with the main module to be imported from the existing python-fuse (https://github.com/libfuse/python-fuse), which is also fuse. We noticed this in Debian, which carries packages for both modules in its archive, and tried to work around this issue by renaming the module to fusepy.py in Debian. However, there is still a danger of having a script import the wrong module if someone has both installed.

To address this issue, I was wondering if you could find a solution on the upstream side? This looks like the cleanest solution to me.

This refers to Debian bug #899194 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899194)

[eestrada]

Hi @satta. We can probably make this name change. In fact we are planning on refactoring the code a bit anyway to merge all the shared code between fuse.py and fusell.py, so when we make that happen it might be a good time to pull the trigger on this as well.

I think a name change like this will probably necessitate a major version bump as well, since it will break all code depending on the current name.

[satta]

Excellent, thanks!