Obf-Projects

Biopython 1.84 has been released and is available from our website and PyPI.

This contains about 5 months worth of updates, so the change-log in the news file is longer than usual. There have also been a few deprecations, most noteworthy this may be our last release with Python 3.9 support.

Many thanks to the Biopython developers and community for making this release possible, especially the following contributors:

• Anil Tuncel (first contribution)
• David Cain
• Fabio Zanini (first contribution)
• Joao Rodrigues
• Judith Bernett (first contribution)
• Luca Monari (first contribution)
• Meridia Jane Bryant (first contribution)
• Manuel Lera-Ramirez
• Michael M. (first contribution)
• Michiel de Hoon
• Peter Cock
• Rudolf Koopmann (first contribution)
• Will Tyler (first contribution)

Dear Biopythoneers,

Biopython 1.74 has been released and is available from our website and PyPI.

This release of Biopython supports Python 2.7, 3.4, 3.5, 3.6 and 3.7. However, it will be the last release to support Python 3.4 which is now at end-of-life. It has also been tested on PyPy2.7 v6.0.0 and PyPy3.5 v6.0.0.

(Please note we will be dropping support for Python 2.7 in early 2020.)

Over half our code is now explicitly available under either our original “Biopython License Agreement”, or the very similar but more commonly used “3-Clause BSD License”. See the LICENSE.rst file for more details.

Dear Biopythoneers,

Biopython 1.73 has been released and is available from our website and PyPI.

This release of Biopython supports Python 2.7, 3.4, 3.5 and 3.6. It has also been tested on PyPy2.7 v6.0.0 and PyPy3.5 v6.0.0.

As in recent releases, more of our code is now explicitly available under either our original " Biopython License Agreement", or the very similar but more commonly used “3-Clause BSD License”.  See the LICENSE.rst file for more details.

Dear Biopythoneers,

I’m writing this in Portland at the GCC BOSC 2018 conference, where I will present the Biopython Project Update 2018 talk tomorrow. Yesterday during my airport layover in Iceland, I published the Biopython 1.72 release to our website and PyPI:

https://biopython.org/wiki/Download https://pypi.python.org/pypi/biopython/1.72

This release of Biopython supports Python 2.7, 3.4, 3.5 and 3.6. It has also been tested on PyPy2.7 v6.0.0 and PyPy3.5 v6.0.0.

Internal changes to Bio.SeqIO have sped up the SeqRecord .format method and SeqIO.write (especially when used in a for loop).

BioJava 5.0.0 was released on the 23rd of March 2018. This represents a major milestone that brings more consolidation and reorganisation of modules. This is the first release to be based on Java 8, bring in your lambdas and stream API calls!

The release represents work done in the last 2 years, alpha releases were available for quite some time and now this makes all the changes officially public.

Some major refactoring occurred in the biojava-structure module. The data model to deal with macromolecular structures has been adapted to be closer to the mmCIF data model. Other improvements in biojava-structure are support for MMTF format and improved symmetry detection code.

Dear Biopythoneers,

Source distributions of Biopython 1.71 are now available from the downloads page on the official Biopython website, and the release is also on the Python Package Index (PyPI) including pre-compiled Wheel Packages for Linux, Mac OS X and Windows.

This release of Biopython supports Python 2.7, 3.4, 3.5 and 3.6 (we have now dropped support for Python 3.3). It has also been tested on PyPy2.7 v5.10.0 and PyPy3.5 v5.10.1.

Python 3 is the primary development platform for Biopython. We will drop support for Python 2.7 no later than 2020, in line with the end-of-life or sunset date for Python 2.7 itself.

Podcast.__init__ describes itself as “The Podcast About Python and the People Who Make It Great”, and the most recent episode is " Biopython with Peter Cock, Wibowo Arindrarto, and Tiago Antão (Episode 125)".

Listening to the finished podcast, interviewer Tobias Macey did a great job. There are things I would have liked to have said - but it turned out pretty well. I hope you’ll agree:

Its worth looking back over the podcast archives, here are a few that caught my eye:

Dear Biopythoneers,

Source distributions of Biopython 1.70 are now available from the downloads page on the official Biopython website, and the release is also on the Python Package Index (PyPI). Windows installers and/or wheels should be available later. ( Update: Compiled wheel packages now available for Linux, Mac OS X and Windows).

This release of Biopython supports Python 2.7, 3.4, 3.5 and 3.6 (we have now dropped support for Python 3.3). It has also been tested on PyPy v5.7, PyPy3.5 v5.8 beta, and Jython 2.7 (although we are deprecating support for Jython).

Dear Biopythoneers,

Source distributions and Windows installers for Biopython 1.69 are now available from the downloads page on the official Biopython website, and the release is also on the Python Package Index (PyPI).

We are happy to announce the long-awaited release of BioPerl v1.7.0.  The release is now available on CPAN and Github.

During this release series, we will move some extraneous code to separate repositories and CPAN releases, primarily to reduce the number of dependencies required for BioPerl installation (in many cases for modules that are never used) and also reduce maintenance overhead.

This may only impact you if your code incorrectly list the immediate downstream dependencies that you utilize.  For example, we have now moved Bio::Coordinate code to a separate repo and will release it as a separate distribution on CPAN.  If your tools require Bio::Coordinate::Result and list this module as a dependency, you should be fine: a separate Bio::Coordinate release should pull in the latest BioPerl, until then it would pull in the last BioPerl release with that module.  However, if you list Bio::Root::Root or Bio::Perl as a dependency to pull in Bio::Coordinate::Result, your installation will not work correctly (as Bio::Root::Root is not the proper code dependency).  We can work with distributions affected to help with this transition and will be more consistently evaluating reverse dependencies on CPAN for upcoming releases as we split out code.  Please post issues on Github if you see problems with your code and the latest release.