This entry was posted
on Friday, January 26th, 2007 at 12:14 pm and is filed under Uncategorized.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
I suspect that the problem is related to the ‘!’ in the filenames. I have added a filter to remove ‘!’ from filenames in svn. You can either wait for the next release or checkout the current code from the svn repository.
If I try to install fusedaap 0.3.1 I get the following error when I use the current fuse-py:
No handlers could be found for logger “fusedaap”
Traceback (most recent call last):
File “fusedaap.py”, line 626, in
main()
File “fusedaap.py”, line 596, in main
server = DaapFS()
File “fusedaap.py”, line 159, in __init__
fuse.Fuse.__init__(self, *args, **kw)
File “/usr/lib/python2.5/site-packages/fuse.py”, line 678, in __init__
“”"
RuntimeError: fuse.fuse_python_api not defined.
! Please define fuse.fuse_python_api internally (eg.
!
! (1) fuse.fuse_python_api = (0, 2)
!
! ) or in the enviroment (eg.
!
! (2) FUSE_PYTHON_API=0.1
!
! ).
!
! If you are actually developing a filesystem, probably (1) is the way to go.
! If you are using a filesystem written before 2007 Q2, probably (2) is what
! you want.”
So I added fuse.fuse_python_api = (0, 1)
after
import fuse
Now I get the following message many times:
File “/usr/lib/python2.5/site-packages/fuse.py”, line 889, in __getattr__
m = self.methproxy(meth)
and then:
RuntimeError: maximum recursion depth exceeded
Is it possible to make fusedaap compatible with the most recent fuse-py?
February 2nd, 2007 at 1:48 pm
I have some problems with it on MacOSX with MacFuse. I am using 0.3.1 .
What debugging info would you be interested in?
:~/Desktop/FuseDaap/artists/Dire_Straits/Communique$ ls -la
ls: ANGEL_OF_MERCY06!!s.mp3.mp3: Invalid argument
ls: COMMUNIQUE04!!s.mp3.mp3: Invalid argument
ls: FOLLOW_ME_HOME09!!s.mp3.mp3: Invalid argument
February 17th, 2007 at 2:11 pm
Ola,
I suspect that the problem is related to the ‘!’ in the filenames. I have added a filter to remove ‘!’ from filenames in svn. You can either wait for the next release or checkout the current code from the svn repository.
-Peter
February 19th, 2007 at 2:05 pm
I may me dense but how do I go about using this python code with macfuse?
February 26th, 2007 at 9:09 pm
Hi, are you also working on a version for iTunes after 7.0 ? cu Annon
April 6th, 2007 at 11:00 am
Hi, I’m the Amarok developer and developed its DAAP support.
iTunes 7 DAAP support is unlikely in the open source world unless someone really has the time I think…
August 5th, 2007 at 7:07 am
If I try to install fusedaap 0.3.1 I get the following error when I use the current fuse-py:
No handlers could be found for logger “fusedaap”
Traceback (most recent call last):
File “fusedaap.py”, line 626, in
main()
File “fusedaap.py”, line 596, in main
server = DaapFS()
File “fusedaap.py”, line 159, in __init__
fuse.Fuse.__init__(self, *args, **kw)
File “/usr/lib/python2.5/site-packages/fuse.py”, line 678, in __init__
“”"
RuntimeError: fuse.fuse_python_api not defined.
! Please define fuse.fuse_python_api internally (eg.
!
! (1) fuse.fuse_python_api = (0, 2)
!
! ) or in the enviroment (eg.
!
! (2) FUSE_PYTHON_API=0.1
!
! ).
!
! If you are actually developing a filesystem, probably (1) is the way to go.
! If you are using a filesystem written before 2007 Q2, probably (2) is what
! you want.”
So I added fuse.fuse_python_api = (0, 1)
after
import fuse
Now I get the following message many times:
File “/usr/lib/python2.5/site-packages/fuse.py”, line 889, in __getattr__
m = self.methproxy(meth)
and then:
RuntimeError: maximum recursion depth exceeded
Is it possible to make fusedaap compatible with the most recent fuse-py?
Thanks,
Jorik Caljouw