I ended up doing something similar to catch any future problematic characters:
https://github.com/biopython/biopython/pull/1607 Peter On Fri, Apr 6, 2018 at 10:36 AM, Peter Cock <p.j.a.c...@googlemail.com> wrote: > Thanks Andreas, > > Piotr, I think your fix would be worth including in Biopython. > > Do you want to submit this as a pull request, or give me > permission to do so by email? > > We'd need you to agree to both the Biopython License Agreement > and the 3-clause BSD licence, and say if you'd like to be > acknowledged by name or not. > > Regards, > > Peter > > On Fri, Apr 6, 2018 at 8:16 AM, Andreas Tille <ti...@debian.org> wrote: >> Hi Peter, >> >> On Thu, Apr 05, 2018 at 04:19:50PM +0100, Peter Cock wrote: >>> >>> https://github.com/biopython/biopython/commit/6421d365a511c0de71748737ba6e1cd8518658ac >>> >>> Can you pull in that commit as a patch for the Biopython 1.71 package? >> >> Thanks. I'm using this as patch. I can confirm that this works now >> (I'm using the other patch suggested here[1] in addition to deal with >> potential other encoding issues. >> >> I'll upload soon (I had some other issues with the packaging which are >> not related). >> >> Kind regards >> >> Andreas. >> >> >> [1] https://lists.debian.org/debian-python/2018/04/msg00023.html >> >> -- >> http://fam-tille.de
