[Biopython-dev] Python 3 and subprocess .communicate() bug

Peter Cock p.j.a.cock at googlemail.com
Thu May 30 04:34:15 EDT 2013


On Thu, May 30, 2013 at 9:28 AM, Tiago Antão <tiagoantao at gmail.com> wrote:
> I was having a look at the issue precisely now.
>
> I do not have a cast opinion on the issue, I think it all boils down on how
> many people are dependent on 3.2.3 and prior 3s.
>
> In theory I would prefer not to have workarounds for implementation bugs (as
> makes things more complex to manage in the long-run), but if many people are
> using buggy 3.x, I see no option...
>
> I simply do not have any view on how many people would be using these...
>

Since till now we've not officially supported Python 3, but
plan to start doing so for the forthcoming Biopython 1.62
release, so we could just set a minimum version of 3.2.4
(with Python 3.3 being our current recommendation).

However, that may be a problem for some current Linux
distributions still shipping older versions?

Peter



More information about the Biopython-dev mailing list