From: Stas Z <sta...@gm...> - 2005-09-21 19:48:52
|
On 9/21/05, Sebastien Delafond <sde...@gm...> wrote: > Unfortunately this doesn't fix gmailfs: I am still getting errors on First of all, I know nothing about gmailfs, but I see some trouble spots. [...] > ~ # sudo touch /mnt/test > Empty account > Traceback (most recent call last): > File "/usr/share/gmailfs/gmailfs.py", line 1094, in getinodemsg > return thread._messages[len(thread._messages)-1] > IndexError: list index out of range Just guessing here, but I suspect this is the GmailThread._messages attribu= te. If so it's better not to use attributes directly but to use the API Further more if indeed GmailThread._messages is used, this class hasn't changed since libgmail version 0.1.0. [....] > And then listing it doesn't yield an exception, but something even > weirder: > > ~ # sudo ls /mnt/bar > Empty account Yet another result of accessing class attributes directly rather then through an API. It's part of a exception catch I added to test for empty message threads. I suspect because gmailfs interacts with the internal message threads rather then through an API, it gets into trouble because there are changes to these int= ernal class attributes. > > Has there been an API change somewhere, among all those > bugfixes/security fixes ? Changes yes, to an API no. I hope richard can comment on this, because I don't know how gmailfs (ab)us= es libgmail. Stas -- A nation that continues year after year to spend more money on military def= ense than on programs of social uplift is approaching spiritual doom. Martin Luther King, Jr. |