[tahoe-dev] patch: tahoe_fuse.py passes unit test.

[Nathan]

Hi.

Thanks for the feedback!  I think you may be my first user.

I believe the issue here is this:  I wrote tahoe-fuse for an old
strange version of python-fuse.  I haven't gotten it working with the
latest api (which apparently changes the api).

In the old version, the log output goes straight to std-out of the
terminal where you run tahoe-fuse.py.  In the new version this is
obscured somehow.

I'll see if I can fix that up sometime this week.

The single unit test isn't very relevant here.  This module has like
0.02% code coverage by tests.  ;-)

Nathan


On Jan 15, 2008 3:40 PM, Peter Secor <secorp at allmydata.com> wrote:
> Hi Nathan,
>
>    I'm trying to play with this on a Mac, and have arrived at the
> following point.
>
>   * I've installed MacFUSE and verified that it works (sshfs)
>   * I've installed the python bindings and verified that they work (gmailfs)
>   * I'm now trying to run tahoe_fuse.py, and it will mount the directory
> but when trying to do an 'ls' it says that ". is not a directory".
>   * The one unit test passes
>
> Where can I look for logs on this? I can't seem to find that in your README.
>
> Talk soon,
> Peter
>
> Nathan wrote:
> > This makes the only unit test for tahoe_fuse.py pass by url unquoting caps.
> >
> > This patch is a superset of one I previously sent.
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > tahoe-dev mailing list
> > tahoe-dev at allmydata.org
> > http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
>