Code

As per Peter’s recent post we are using this space to show of a couple of the new features in Biopython 1.52 before it is released. In this post we’ll look at the new convert() function that both Bio.SeqIO and Bio.AlignIO will get in Biopython 1.52.

No one has ever complained that bioinformatics just doesn’t have enough file formats - you probably frequently find yourself converting sequence files to suit particular applications with Bio.SeqIO. At the moment this is usually a two step process, something like this:

The forthcoming release of Biopython 1.52 will include a couple of nice improvements to the Bio.SeqIO module, and here we’re going to introduce the new index function. This will of course be covered in the Biopython Tutorial & Cookbook ( PDF) once this code is released.

Suppose you have a large sequence file with many many individual sequences in it. This could be next generation sequence data for example, maybe a FASTQ, FASTA or QUAL file. Or, it might be a big annotation rich file, such as the whole of UniProt, or a chunk of GenBank.

We are pleased to announce the release of BioRuby 1.3.1. This new release fixes many bugs existed in 1.3.0.

Here is a brief summary of changes.

• Refactoring of BioSQL support.
• Bio::PubMed bug fixes.
• Bio::NCBI::REST bug fixes.
• Bio::GCG::Msf bug fixes.
• Bio::Fasta::Report bug fixes and added support for multiple query sequences.
• Bio::Sim4::Report bug fixes.
• Added unit tests for Bio::GCG::Msf and Bio::Sim4::Report.
• License of BioRuby is clarified.

In addition, many changes have been made, mainly bug fixes. For more information, you can see ChangeLog.

We are pleased to announce the release of Biopython 1.51.This new stable release enhances version 1.50 (released in April) by extending the functionality of existing modules, adding a set of application wrappers for popular alignment programs and fixing a number of minor bugs.

In particular, the SeqIO module can now write Genbank files that include features, and deal with FASTQ files created by Illumina 1.3+. Support for this format allows interconversion between FASTQ files using Solexa, Sanger and Ilumina variants using conventions agreed upon with the BioPerl and EMBOSS projects.

A beta release for Biopython 1.51 is now available for download and testing.

In the two months since Biopython 1.50 was released, we have introduced support for writing features in GenBank files using Bio.SeqIO, extended SeqIO’s support for the FASTQ format to include files created by Illumina 1.3+, and added a new set of application wrappers for alignment programs, and made numerous tweaks and bug fixes.

All the new features have been tested by the dev team but it’s possible there are cases that we haven’t been able to foresee and test, especially for the GenBank feature writer (as there as just so many possible odd fuzzy feature locations).

Constructing complicated NCBI Entrez searches can be tricky, but it turns out one of the Entrez Programming Utilities called Entrez EInfo can help.

For example, suppose you want to search for mitochondrial genomes from a given taxa - either just in the Entrez web interface, for use in a script with EFetch.

I knew from past experience about using name[ORGN] in Entrez to search for an organism name - but how would you specify just mitochondria? I actually worked this out from the NCBI help and exploring the Entrez website’s advanced search - but it took a while.

As announced here, any last minute requests to postpone dropping support for Python 2.3 from the next release of Biopython must be posted to the main Biopython mailing list no later than Friday, May 8.

Hi all,

You may have noticed we’re trying out using the wiki for Biopython cookbook entries. It’s a new idea so at the moment there are only a few ‘recipes’ on offer. If you have some tricks you find yourself using time and again to solve a problem why not share them? Similarly, if you find yourself coming up against a problem you can’t seem to solve easily with Biopython’s tools send a message to one of the mailing lists proposing it as a cookbook example and someone just might solve it for you!

Those of you doing next generation sequencing may be pleased to know that the next release of Biopython is expected to include support for reading and writing FASTQ and QUAL files within our Bio.SeqIO interface. These formats are used for traditional Sanger capillary sequencing, and Roche 454 sequencing (Roche provide tools to convert from their binary SFF files) with PHRED quality scores. Solexa/Illumina sequencers produce a FASTQ variant where the quality scores are encoded differently, and this is also supported.

Initially for evaluation purposes only, Giovanni and Bartek have setup a mirror of Biopython on GitHub, which is automatically updated from the OBF hosted Biopython CVS repository. See our git migration wiki page for details. If this is favorably received, then moving Biopython from CVS to git seems likely at some point this year.

Originally, all the OBF hosted projects used CVS for their source code repositories. At the start of 2008, BioPerl and BioJava moved over to Subversion (SVN), followed by BioSQL. Biopython was originally going to do the same, but this didn’t actually happen. Having all the Bio* projects using the same version control system would have simplified server administration for the OBF, but using SVN wouldn’t really have made that much difference to Biopython development. Discussion on the Biopython development mailing list has since shifted towards next-generation distributed version control systems like git or Bazaar.