I hear you, re. guessing about data - it just sounded like this would be a rare case. Is it happening on particular database searches? Now that I look at it I'm wondering in what situation the IndexError would be triggered. I'm diving into the details here just because I don't want to discover later on there that I'd made some assumptions about the id parsing. Thanks, Damion On Wed, Nov 20, 2013 at 7:31 PM, Dooley, Damion <Damion.Dooley@bccdc.ca> wrote:
Woops - I realize now findtext() must be unescaping all ">", so Peter was trying to address other non-splitting occurances of " >" as per his patch notes. But perhaps a stop_err() isn't merrited in this case?
So ignore my test for ">" comment.
Regards,
Damion
OK - good. I was worried that there might be some inconsistency between different databases of versions of BLAST about how the > was encoded. As to why I treat this as a fatal error (calling stop_err), the alternative would be to issue a warning to stderr, and guess what the data ought to look like? That just seems like asking for trouble - a big red error should ensure I hear bug reports ;) Zen of Python: Errors should never pass silently. Peter