[Biopython-dev] uploading coalescent code
Michiel De Hoon
mdehoon at c2b2.columbia.edu
Tue Nov 13 11:32:08 UTC 2007
> But, there is a more serious change: setup.py. For this I suggest:
> 1. Adding you to the SimCoal feature bug 2375, can I do that?
> 2. I would put my suggested diff there and you could
> evaluate/change/accept/reject it
Sure, that is fine.
Michiel de Hoon
Center for Computational Biology and Bioinformatics
1150 St Nicholas Avenue
New York, NY 10032
On Nov 13, 2007 9:52 AM, Michiel De Hoon <mdehoon at c2b2.columbia.edu> wrote:
> Hi Tiago,
> > 3. IMPORTANT: There are some text template files. I suppose that there
> > is no standard way to have datafiles around. I was thinking (actually
> > somebody suggested on this list) in putting it alongside the code.
> > Question: Is there any standard way to know where biopython is installed
> > (so that I can read those datafiles)? We are talking of very small files.
> Have you looked at the manual for distutils? Section 2.6 and 2.7 discuss
> having data files distributed with a Python extension. See
> Given that such an option exists, somebody must already be using it. So I
> think your best option is to google around a bit to find some examples.
More information about the Biopython-dev