[Biopython-dev] BioSQL Loader.py patch

[Leighton Pritchard]

Hi all,

Apologies for the multiple postings - I'm getting warnings about
suspicious headers, and on the last repost I forgot the subject line...

I'm not sure if you want this here, or on the BioPython BugZilla, but
I've written a patch that modifies BioSQL/Loader.py to load db_xref
qualifier/value pairs, and also contains a patch to correct bug 1921
caused by the attempted default insertion of an invalid taxon_id.
The .diff is attached.  I've been living with the patched code for a
month without any issues, so it's been stable as far as I've needed it
to be (and has worked with all bacterial GenBank .gbk files and the
BioPython GenBank parser).

There are two sections of the patched code that print/write to stdout.
Is this an acceptable way of reporting to the user in a BioPython style?

Cheers,

L.

-- 
Dr Leighton Pritchard AMRSC
D131, Plant-Pathogen Interactions, Scottish Crop Research Institute
Invergowrie, Dundee, Scotland, DD2 5DA, UK
T: +44 (0)1382 562731 x2405 F: +44 (0)1382 568578
E: lpritc at scri.sari.ac.uk   W: http://bioinf.scri.sari.ac.uk/lp
GPG/PGP: FEFC205C E58BA41B  http://www.keyserver.net             
(If the signature does not verify, please remove the SCRI disclaimer)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

DISCLAIMER:

This email is from the Scottish Crop Research Institute, but the views 
expressed by the sender are not necessarily the views of SCRI and its 
subsidiaries.  This email and any files transmitted with it are confidential 
to the intended recipient at the e-mail address to which it has been 
addressed.  It may not be disclosed or used by any other than that addressee.
If you are not the intended recipient you are requested to preserve this 
confidentiality and you must not use, disclose, copy, print or rely on this 
e-mail in any way. Please notify postmaster at scri.sari.ac.uk quoting the 
name of the sender and delete the email from your system.

Although SCRI has taken reasonable precautions to ensure no viruses are 
present in this email, neither the Institute nor the sender accepts any 
responsibility for any viruses, and it is your responsibility to scan the email 
and the attachments (if any).