[Flickrfs-users] fuse-python version

[<rdm...@bi...>]

On Sat, 26 Jan 2008 at 11:32, Manish Rai Jain wrote:
> Sounds great. Let me know what help you need from me.

OK, so flickrfs was written against fuse-python 0.1, right?  Setting
fuse.fuse_python_api to (0, 1) gets flickrfs to run against fuse-python
2.0 (you can do this without touching the code by setting the environment
variable FUSE_PYTHON_API to '0.1'), but it doesn't work right, at least on
my system.  It appears that flickrfs is doing things to the filesystem
before it is mounted.  That is, the mount happens when sever.main()
is called, but directories are created and threads are launched in the
__init__, before main() is called.  This causes flickrfs to hang on my
system some time after the mount is done.

Are others successfully running flickrfs using fuse-python 0.2?
If you are running 0.1, are you having the problem with the empty
'sets' directory?

The 'new api' page for fuse-python says that this is where the mount
took place in 0.1 as well (in main()), but I'm wondering if maybe that
isn't in fact true, and under 0.1 the mount happened in the __init__.
The problem is that I can't get fuse-python 0.1 to compile on my system,
so I can't test it :(

I'm going to fiddle with the flickrfs initialization and see if I can get
it running on my system.  The question is, is anybody using fuse-python
0.1 who can't or doesn't want to upgrade?  My thought is that we should
eventually migrate flickrfs to the 0.2 API, so if I need instead to
maintain backward compatibility I'd better know now :)

--David