@@ -40,6 +40,9 @@ efneighbor) whose Biopython wrappers are now obsolete. See also the DEPRECATED file, as several old deprecated modules have finally been removed (e.g. Bio.EUtils which had been replaced by Bio.Entrez). +On a technical note, this will be the last release using CVS for source code +control. Biopython is moving from CVS to git. + =================================================================== August 17, 2009: Biopython 1.51 released. NEWS @@ -1,3 +1,13 @@ +**NOTE ABOUT CVS** + +Until late September 2009, Biopython source code was hosted in CVS running +on the Open Bioinformatics Foundation (OBF) servers. We are now using git, +a distributed version control system. The CVS repositories at the OBF will +remain for a while as "read only" static backups of everything up to and +including Biopython 1.52 but will not be updated in future. See our website +for further details, http://www.biopython.org/ + + **Biopython README file** "The Biopython Project":http://www.biopython.org/ is an international @@ -102,16 +112,15 @@ data format has changed and broken the parsing code. (The BLAST and GenBank formats seem to be particularly fragile.) Thus, the parsing code in Biopython is sometimes updated faster than we can build Biopython releases. You can get the most recent parser by pulling the relevant -files (e.g. the ones in Bio.SeqIO or Bio.Blast) out of -"anonymous cvs":http://cvs.biopython.org/ or our git mirror on +files (e.g. the ones in Bio.SeqIO or Bio.Blast) out git mirror on "github":http://github.com/biopython/biopython/ . -However, be careful when doing this, because the code in CVS/github is +However, be careful when doing this, because the code in github is not as well-tested as released code, and may contain new dependencies. Finally, you can send a bug report to the bug database or biopython@biopython.org. In the bug report, please let us know 1) which operating system and hardware you are using, 2) Python version, -3) Biopython version (or CVS/git version/date), 4) traceback that occurs, +3) Biopython version (or git version/date), 4) traceback that occurs, 5) offending code, and 6) data file that causes the problem. README 2a3310b306eb983042099815865fe0592888127c peterc peterc http://github.com/etal/biopython/commit/5289555b7de49db9d55970e029b3dc8ed431d375 5289555b7de49db9d55970e029b3dc8ed431d375 2009-09-23T02:55:51-07:00 2009-09-23T02:55:51-07:00 Adding notes about CVS/git 435f121c411643eeac3acd7797d60a4818494c5e peterc peterc