Hi Kenny, it turns out I completely misinformed you in my original reply to this question. Pygr *does* support annotation attributes, and even allows you to specify attribute aliases via AnnotationDB's sliceAttrDict argument (which provides a mapping to the attribute name actually used on the sliceInfo object, or, if the sliceInfo is a tuple, to the numerical index to use to retrieve the desired attribute).
To summarize: - any attribute request to AnnotationSeq / AnnotationSlice will be checked against the sliceInfo object using the same attribute name. - if that attribute name is found in sliceAttrDict, the corresponding alias will be used to retrieve the attribute It turns out AnnotationDB's itemAttrDict argument does nothing and was marked in the code for deletion! For the moment, completely ignore it. I think I was planning to replace the current __getattr__ based attribute mirroring with descriptors, but just haven't gotten around to it. No one has complained, so I think the current situation will remain unchanged in the final 0.8 release. Does this answer your question and provide what you needed? If you want some example code, let me know. -- Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
