Menu

#3 Fuse instance has no attribute 'mountpoint

open
nobody
None
5
2006-06-11
2006-06-11
No

I get this very nondescript error when trying to use
FlickrFS:

[augie@pear flickrfs-1.2.9]$ python flickrfs.py
/tmp/flickrfs
Traceback (most recent call last):
File "flickrfs.py", line 1218, in ?
server = Flickrfs()
File "flickrfs.py", line 475, in __init__
log.info("flickrfs.py:Flickrfs:mountpoint: %s" %
repr(self.mountpoint))
File "/usr/lib/python2.4/site-packages/fuse.py", line
710, in __getattr__
raise AttributeError, "Fuse instance has no
attribute '%s'" % meth
AttributeError: Fuse instance has no attribute 'mountpoint'

flickrfs 1.2.9
fuse 2.3
fuse-py-089c6a510fd3

The test.py from flickrfs works fine, and so does the
example/xmp.py from fuse-py . So I'm not really sure
what this errors is supposed to mean.

Discussion

  • Augie Schwer

    Augie Schwer - 2006-06-15

    Logged In: YES
    user_id=638463

    The same thing happens on another box with all the latest
    and greatest:

    fuse-2.5.3
    flickrfs from CVS
    fuse-py from CVS

     
  • gabriele de benedittis

    Logged In: YES
    user_id=1394600

    the latest fuse-python bindings are incompatible.
    just set the env variable FUSE_PYTHON_COMPAT=0.1 and mount
    again.

    from the README.new_fusepy_api:

    Enforcing compatibility
    -----------------------

    There are lot of existing Python based FUSE based
    filesystems out there.
    They won't work with the current fuse-py code as is;
    however, we'd like
    to keep on using them. What can we do?

    Easy it is: just set ``fuse.compat_0_1`` to ``True`` before
    you invoke
    your filesystem. This can be achieved externally too, by
    setting the
    ``FUSE_PYTHON_COMPAT`` environment variable to ``0.1``.

    ciao

     
  • Nobody/Anonymous

    Logged In: NO

    has anyone figured this bug out?

    please let me know: totaldis@gmail.com

     
  • Frederik 'Freso' S. Olesen

    Logged In: YES
    user_id=287697
    Originator: NO

    I can verify that setting the environment variable 'fixes' this issue for me.

     

Log in to post a comment.

MongoDB Logo MongoDB