Re: Biopython 1.68 plans (mid August?)
Peter Cock <[email protected]> Mon, 22 Aug 2016 09:16:43 +0100
| Newsgroups | gmane.comp.python.bio.devel |
|---|---|
| Message-ID | <CAKVJ-_6QNp8jZfmkjwxzZVFikaKvuBTug-O7P1yg4hpDa6hA-w@mail.gmail.com> |
Yes :( I did try emailing the NCBI a week or two ago, but evidently didn't reach the right person. I'll try to do the Biopython release this week... Peter On Mon, Aug 22, 2016 at 7:53 AM, Michiel de Hoon <[email protected]> wrote: > As a related point, the NCBI website lists Biopython 1.67 as the > https-compliant version, while this should be 1.68 if I understand > correctly. > See the table on this page: > http://www.ncbi.nlm.nih.gov/home/develop/https-guidance.shtml > > > > Best, > -Michiel > > > On Friday, August 12, 2016 4:37 PM, Peter Cock <[email protected]> > wrote: > > > Thanks Ben, > > I used to use cygwin on Windows XP, and I would certainly > be giving Windows Ubuntu Bash a test if I had a Windows 10 > machine - a very interesting development. I presume it can > run its own copy of a (Linux Ubuntu) Python too? > > Peter > > On Thu, Aug 11, 2016 at 8:09 PM, Fulton, Ben <[email protected]> wrote: >> Yes, I can do the installers (although I am moving away from strict >> Windows to Windows Ubuntu Bash). >> >> -- >> Ben Fulton >> Research Technologies >> Scientific Applications and Performance Tuning >> Indiana University >> E-Mail: [email protected] >> >> -----Original Message----- >> From: Biopython-dev >> [mailto:[email protected]] On >> Behalf Of Peter Cock >> Sent: Thursday, August 11, 2016 5:15 AM >> To: Biopython-Dev Mailing List <[email protected]>; >> Christian Brueffer <[email protected]>; Ben Fulton <[email protected]>; >> [email protected] >> Subject: [Biopython-dev] Biopython 1.68 plans (mid August?) >> >> Dear Biopythoneers, >> >> The NCBI plan to switch to HTTPS on 1 September 2016, so it >> would be good to get a new Biopython release out before that >> with the changes to use HTTPS by default (which we know >> works). >> >> To that end, I would like us to do the Biopython 1.68 release >> this month (August), perhaps aiming for next week? >> >> Christian - we talked briefly about this at BOSC 2016 - but >> would you be willing to try to work though the currently release >> instructions (as far as possible without pushing any changes >> to GitHub or PyPI) to help pin point what I have left unclear >> with the recent website changes? >> >> http://biopython.org/wiki/Building_a_release >> >> Ben - would you be able to build the Windows installers >> again please? >> >> Bow - are you ready to remove the experimental warning >> from Bio.SearchIO? Or at least, most of it - I know you have >> some changes in mind for the Exonerate parser: >> https://github.com/biopython/biopython/pull/815 >> >> Everyone - is there anything urgent we need to review and >> merge? What am I overlooking? There are lots of pull >> requests we could merge, and some are close to ready. >> >> Thanks, >> >> Peter >> _______________________________________________ >> Biopython-dev mailing list >> [email protected] >> http://mailman.open-bio.org/mailman/listinfo/biopython-dev > _______________________________________________ > Biopython-dev mailing list > [email protected] > http://mailman.open-bio.org/mailman/listinfo/biopython-dev > >