Thanks, Brent! The None default in that line was introduced in our recent code review of seqdb. I'll look into this with Titus... Seems like a try-accept clause in the original code was replaced with the None default, but doesn't actually handle the None case properly.
-- Chris On Mar 30, 2009, at 11:17 AM, Brent Pedersen wrote: > > On Thu, Mar 26, 2009 at 7:26 PM, Brent Pedersen <bpede...@gmail.com> > wrote: >> > hi, this error occurs because of this: > http://repo.or.cz/w/pygr.git?a=blob;f=pygr/seqdb.py;h=f02ee0fb786bed01d58b8e6c5c813c34639b5027;hb=HEAD#l569 > where it uses: > anno_seq_attr = getattr(seq, '_anno_seq', None) > if anno_seq_attr.db in self.db.dicts: > > where .db is undefined if the getattr() call returns None. i think > that the None case should > be handled or raise an informative error as currently, it's > "AttributeError: 'NoneType' object has no attribute 'db'" > > i'm still not aware of how to fix this, or why it occurs only when i > reload data from > pygr.Data, and not when i create the MSA from scratch. i'll create a > self-contained > case if it helps. > > thanks, > -brent --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-dev@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 -~----------~----~----~----~------~----~------~--~---
