I have been banging my head against the exact same problem, but haven't always been able to reproduce it. I'm on pygr 0.8.1, sqlite3 version 3.6.22, python 2.6.5 and Ubuntu 10.04
On Apr 3, 8:34 pm, "C. Titus Brown" <c...@msu.edu> wrote: > Hi all, > > twice so far, I've run across a situation where a unicode sequence ID > (coming from sqlite) was causing a pygr AnnotationDB to fail horribly. > Both times, I was in a hurry and put in a quick hack to coerce the sequence ID > to str, but neither time could I reproduce the bug at a later time: by > default, it seems dictionaries do the right coercion! > > So, I'm submitting this patch: > > http://github.com/ctb/pygr/commits/sqlite_str/ > > http://github.com/ctb/pygr/commit/ba995f654c62237f6ce72fc546f8a435e7f... > > in the hopes that I'll never have to track down the bug in detail. Grr. > > (I have some test code that I can clean up and submit but it doesn't trigger > the bug without the patch, anyway, so I'm not sure what use it is.) > > cheers, > --titus > -- > C. Titus Brown, c...@msu.edu -- You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-...@googlegroups.com. To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en.
