Re: Ideas for Biopython 2.0

--===============0129882904681968263==
Content-Type: multipart/alternative; boundary="001a1141032878fa690552d33601"

--001a1141032878fa690552d33601
Content-Type: text/plain; charset="UTF-8"

Copied from the other thread where I mistakenly posted:

I think we should focus on other topics such as modularity. What do the
proponents of the said modularity say about it? What are its advantages? I
personally think a big disadvantage is that with one package install you
get a wide array of tools for a variety of subjects. With a constellation
of modules you might end up with an up-to-date core and an out-of-date lone
module somewhere, which makes things much much harder not only to maintain
but also to debug in case of issues.

--001a1141032878fa690552d33601
Content-Type: text/html; charset="UTF-8"

<div dir="ltr">Copied from the other thread where I mistakenly posted:<br><br>I think we should focus on other topics such as 
modularity. What do the proponents of the said modularity say about it? 
What are its advantages? I personally think a big disadvantage is that 
with one package install you get a wide array of tools for a variety of 
subjects. With a constellation of modules you might end up with an 
up-to-date core and an out-of-date lone module somewhere, which makes 
things much much harder not only to maintain but also to debug in case 
of issues. <br><br></div>

--001a1141032878fa690552d33601--

--===============0129882904681968263==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Biopython-dev mailing list
[email protected]
http://mailman.open-bio.org/mailman/listinfo/biopython-dev
--===============0129882904681968263==--