[Biopython-dev] Coalescent code
Michiel De Hoon
mdehoon at c2b2.columbia.edu
Thu Oct 4 00:39:47 UTC 2007
> Michiel, please, please don't include SimCoal code that I will be
> committing on the next public version.
To avoid confusion, please don't commit code to CVS that you don't want to be
included in the next Biopython release.
--Michiel.
Michiel de Hoon
Center for Computational Biology and Bioinformatics
Columbia University
1150 St Nicholas Avenue
New York, NY 10032
-----Original Message-----
From: biopython-dev-bounces at lists.open-bio.org on behalf of Tiago Antão
Sent: Wed 10/3/2007 12:04 PM
To: biopython-dev at lists.open-bio.org
Subject: Re: [Biopython-dev] Coalescent code
Hi
On 10/3/07, Peter <biopython-dev at maubp.freeserve.co.uk> wrote:
> There is a similar precedent with Bio/EUtils/DTDs (where the data files
> are XML DTD files). I guess you could have the 10 plain text data files
> in with the python files (or under a subdirectory). Opinions?
In the mean time, I will start committing the code (I can easily
accommodate the details of the places to put the files later, when
there is a decision).
Michiel, please, please don't include SimCoal code that I will be
committing on the next public version.
Regards,
Tiago
_______________________________________________
Biopython-dev mailing list
Biopython-dev at lists.open-bio.org
http://lists.open-bio.org/mailman/listinfo/biopython-dev
More information about the Biopython-dev
mailing list