On Dec 18, 4:50 pm, Christopher Lee <[email protected]> wrote:
> Possible Solutions:
> - require that all pygr.Data access go through a "root" name, i.e.
> pygr.Data.root.Bio.Seq.Genome.HUMAN.hg17. This requires users to type
Hi Chris,
thanks for the detailed explanations.
One question: what is the rationale for having pygr.Data a module
level namespace. While I can't say that I understand all the
internals, it appears that turning a module behavior into a class
instance like behavior brings about some unexpected problems and
complex or annoying behaviors. The question then is why not make it
into a class right away:
data = pygr.Data()
data.Bio.Test.Download()
that way one could customize the constructor by passing various
parameters, allows subclassing, and overall makes it a lot easier to
add other types of functionality without having to modify the main
module. I am playing around with this right now a bit, to see if it
was feasible.
Istvan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pygr-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/pygr-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
