[Biopython-dev] Ready for Biopython 1.54 release?
Eric Talevich
eric.talevich at gmail.com
Sun May 16 16:20:15 UTC 2010
On Fri, May 14, 2010 at 12:14 PM, Eric Talevich <eric.talevich at gmail.com>wrote:
> On Fri, May 14, 2010 at 2:17 AM, Peter <biopython at maubp.freeserve.co.uk>wrote:
>
>> On Fri, May 14, 2010 at 4:08 AM, Eric Talevich <eric.talevich at gmail.com>
>> wrote:
>> > On Thu, May 13, 2010 at 4:37 AM, Peter <biopython at maubp.freeserve.co.uk
>> >
>> > wrote:
>> >>
>> >> Hello all,
>> >>
>> >> Are there any outstanding issues we should address before making
>> >> the Biopython 1.54 release?
>> >>
>> >> Eric has made a good start on covering Bio.Phylo in the tutorial,
>> >> which can be easily proof read online:
>> >> http://biopython.org/DIST/docs/tutorial/Tutorial-dev.html
>> >> http://biopython.org/DIST/docs/tutorial/Tutorial-dev.pdf
>> >>
>> >
>> > I wrote some more, but something very inconvenient happened to my laptop
>> > just after I pushed the commit to my own branch on GitHub:
>> >
>> http://github.com/etal/biopython/commit/960449b1ea9b713ca8111c40d930fc404340fdc2
>> >
>> > This is a description of every TreeMixin method, ripped from the
>> docstrings
>> > / epydoc output and cleaned up a little. The main thing I still need to
>> > explain is how the find_* arguments work.
>> >
>> > However, if we want to get the release out quickly, then all of this can
>> be
>> > moved to the wiki instead, if you'd prefer.
>> >
>> > -Eric
>>
>> Hi Eric,
>>
>> It sounds like giving you a little more time will make the Phylo
>> chapter much more useful.
>>
>> I'm not going to have time today, and while I could do the release
>> from home my Windows development machine is at work.
>>
>> Shall we aim for a release early next week then? Say Monday or
>> Tuesday?
>>
>> Peter
>>
>
> Sure. I'll aim for pushing my documentation to GitHub on Saturday or
> Sunday.
>
> -Eric
>
I've pushed the latest docs to GitHub. Does the chapter look all right now?
Feel free to modify the text as you see fit; I'm going to be traveling again
today and tomorrow and won't be able to respond quickly.
(My netbook's still misbehaving, so I had to do some things I'm not proud of
-- hence "root" as the committer on the last merge.)
-Eric
More information about the Biopython-dev
mailing list