Open GoogleCodeExporter opened 9 years ago
I should've been more clear that this error is specific to the Tahoe support.
Original comment by myselfasunder@gmail.com
on 17 Sep 2014 at 8:38
Anyone?
Original comment by myselfasunder@gmail.com
on 20 Oct 2014 at 8:23
Where did "encodings" come from?
I've never used Tahoe (so can't test your fix) but it looks like you're correct
in that the setcontents prototype needs to be updated to match
http://docs.pyfilesystem.org/en/latest/base.html#fs.base.FS.setcontents
Original comment by gc...@loowis.durge.org
on 28 Oct 2014 at 2:50
The extra attributes came from the Python3 support. setcontents supports
unicode now. Unfortunately it changed the setcontents signature.
This fix is probably simple enough, but I don't know much about tahoefs myself.
Original comment by willmcgugan
on 28 Oct 2014 at 3:07
So who is going to be responsible for it? I have to make this change
whereever I use it.
Original comment by myselfasunder@gmail.com
on 28 Oct 2014 at 3:32
There is likely more to it than that change. Not sure when I'll have the time
to look at it. You could post to the mailing list, maybe the original author
can adapt it.
Original comment by willmcgugan
on 28 Oct 2014 at 4:17
Original issue reported on code.google.com by
myselfasunder@gmail.com
on 17 Sep 2014 at 8:37