[Biopython-dev] Release blockers? PAML?

[Brandon Invergo]

Hi, 
Regarding PAML, I'm sorry I haven't implemented the binary tests yet.
I'll put it on my to-do for today. Turns out it's a Spanish national
holiday today so I guess I don't have to go to the lab.  

I have a Windows 7 laptop that up until now has been quarantined and
used only for music software, with no other software allowed on it, not
allowed near the interwebs, etc (it's a fickle machine), but last night
I broke the rules and installed Python 2.7 on it. I'll try running the
PAML tests on it and I'll let everyone know how it goes. 

Until later,
-brandon

On Mon, 2011-08-15 at 11:04 +0100, Peter Cock wrote:
> Hi all,
> 
> We're about due to make a Biopython release, and I could
> do it early this week - but then I'm away for a fortnight. I am
> fortunate to be attending the BioHackathon 2011 in Kyoto
> next week, http://2011.biohackathon.org/
> 
> I think we're in a good position with the code on the trunk to
> release Biopython 1.58, bar the PAML code which has not
> yet been tested on Windows. Also, I'd be keen for Tiago and
> Brandon to take a look at the application calling code to see
> if the is any scope for a more common approach between
> the PAML wrappers and the PopGen tools. Note that both
> sets of tools are not 'nicely behaved' Unix style tools (which
> is what the Bio.Applications API targets). To do anything
> useful with these tools you have to do nasty things like
> switch the current working directory and so on.
> 
> If we want to do the release this week, we could just warn
> that the PAML code is consider to be "in beta" and that
> the API may well change in non-backwards compatible
> ways?
> 
> What else should be addressed before the next release?
> 
> There are some open bugs, but at first glance nothing
> critical.
> 
> Regards,
> 
> Peter