The Biopython Project is a long-running distributed collaborative effort, supported by the Open Bioinformatics Foundation, which develops a freely available Python library for biological computation [1]. We present here details of the Biopython releases since BOSC 2016, namely Biopython 1.68, 1.69 and 1.70. Together these had 82 named contributors including 51 newcomers which reflects our policy of trying to encourage even small contributions.Biopython 1.68 (August 2016) was a relatively small release, with the main new feature being support for RSSB’s new binary Macromolecular Transmission Format (MMTF) for structural data.Biopython 1.69 (April 2017) represents the start of our re-licensing plan, to transition away from our liberal but unique Biopython License Agreement to the similar but very widely used 3-Clause BSD License. We are reviewing the code base authorship file-by-file, in order to gradually dual license the entire project. Major new features include: a new parser for the ExPASy Cellosaurus cell line database, catalogue and ontology; support for the UCSC Multiple Alignment Format (MAF), FSA sequencing files, version 4 of the Affymetrix CEL format; updates to the REBASE February 2017 restriction enzyme list; Bio.PDB.PDBList now can download more formats including MMTF; enhanced PyPy support by taking advantage of NumPy and compiling most of the Biopython C code modules.Biopython 1.70 (July 2017) has internal changes to better support the now standard pip tool for Python package installation. Major new features include: support for Mauve’s eXtended Multi-FastA (XMFA) file format, updates to our BLAST XML and MEME parsers, ExPASy support, and phylogenetic distance matrices. This release is noteworthy for our new logo, contributed by Patrick Kunzmann. This draws on our original double helix logo, and the blue and yellow colors of the current Python logo.All releases fixed miscellaneous bugs, enhanced the test suite, and continued efforts to follow the PEP8 and PEP257 coding style guidelines which is now checked automatically with GitHub-integrated continuous integration testing using TravisCI. We now also use AppVeyor for continuous integration testing under Windows. Current efforts include improving the unit test coverage, which is easily viewed online at CodeCov.io.
Search from 250 M+ research papersSearch from 250 M+ research papers
Jul 25, 2019
