Move annotation classes to a separate module

[GoogleCodeExporter]

We should move annotation functionality out of seqdb into a new module
(annotate.py or annotation.py?). AnnotationDB doesn't depend on seqdb; I
don't think the prospective annotation.py would even need to import
seqdb...  Their association is purely conceptual.

One consideration: backwards compatibility for unpickling and thus
pygr.Data.  Unpickling looks for classes based on the module location saved
when the object was originally pickled, so to maintain the ability to
unpickle (e.g. retrieve from pygr.Data) existing annotation resources, we'd
have seqdb import a few key classes (AnnotationDB and kin) from
annotation.py, so that those names continue to be accessible from the seqdb
namespace as before.

Original issue reported on code.google.com by cjlee...@gmail.com on 7 Jan 2009 at 7:48

[GoogleCodeExporter]

Original comment by cjlee...@gmail.com on 8 Jan 2009 at 2:13

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by mare...@gmail.com on 21 Feb 2009 at 2:07

• Changed state: FixedNeedsReview

[GoogleCodeExporter]

Hi Titus,
could you please verify this code reorganization, and then change its status to
Closed if you think it's OK?  Again this could be part of the seqdb code review 
we've
been planning.

Thanks!

Chris

Original comment by cjlee...@gmail.com on 5 Mar 2009 at 12:27

[GoogleCodeExporter]

Original comment by mare...@gmail.com on 13 Mar 2009 at 1:02

• Added labels: reviewby-the.good.doctor.is.in

[GoogleCodeExporter]

yep.

Original comment by the.good...@gmail.com on 22 Mar 2009 at 6:13

• Changed state: Closed