Re: Ideas for Biopython 2.0

On Wed, Jun 21, 2017 at 3:23 PM, Iddo Friedberg <[email protected]> wrote:
> Breaking back compatibility, even if explicitly stated, will probably
> disable some dependent software. As someone said on this thread, this is
> science, and there is a lot of old legacy code that, usually for budgetary
> reasons, cannot be maintained to accommodate breaking changes in underlying
> libraries.
>
> Caught between a rock and a hard place on this one. I don't have a good
> solution, I'm afraid. Just that we have to be mindful of the consequences of
> what we do, and understand the environment we are operating in, and who the
> biopython users are.
>
> Actually, now that I think about it, maybe a user survey would help test the
> waters?

Joao may have been thinking that too when he wrote:

"I'd prefer to have a wish list kind of thing from our users/developers and
then pick a few targets that are important to the community as things we
should work on. "

Peter