[Biopython-dev] Help needed: Windows installers for Python 3.5

[Ben Fulton]

I downloaded the ZIP file rather than check out from Github, but yes,
otherwise that's exact;y what I did.

Ben Fulton

On Wed, Oct 28, 2015 at 6:53 AM, Peter Cock <p.j.a.cock at googlemail.com>
wrote:

> Thanks Ben,
>
> Did you essentially do this (or similar to get a clean folder):
>
> git clone git at github.com:biopython/biopython.git
> cd biopython
> git checkout biopython-166
> C:\Python35\python setup.py bdist_wininst
> C:\Python35\python setup.py bdist_msi
>
> Do we need to update the instructions here for Python 3.5 on
> Windows?: http://biopython.org/wiki/Building_a_release
>
> It would be best for someone with access to the biopython.org
> (so me, Michiel, Brad, Tiago, etc) to upload them under
> http://biopython.org/DIST/ and then we can update the download
> wiki page to link to that (which currently will take a Yahoo OpenID
> but not Google as they dropped support for the older API. Sigh).
>
> ***
> But before that, could someone double check these work nicely?
> ***
>
> I can think of a postdoc here who could do that for me, but he's
> out of the office today.
>
> I downloaded them to my Mac, and the file sizes are as expected.
> On Linux I'd use md5sum, the Mac equivalent formats its output
> a little differently but here are the checksums I see:
>
> $ md5 biopython-1.66.win32-py3.5.*
> MD5 (biopython-1.66.win32-py3.5.exe) = dcc6e61ee98e459147884eb293860bce
> MD5 (biopython-1.66.win32-py3.5.msi) = 84b34f3cad695c71e25f5170fbdeec10
>
> Peter
>
> On Wed, Oct 28, 2015 at 3:48 AM, Ben Fulton <ben at benfulton.net> wrote:
> > I built 32-bit Windows installers for Python 3.5.
> >
> > EXE: https://iu.box.com/s/kmf9h3ypcqe5apr6ay0jk4elcdg6kvyc
> >
> > MSI: https://iu.box.com/s/zm8wvpftu3j1228ss6kq783s874h79ba
> >
> > Would it be best to upload the files to the BioPython wiki? I couldn't
> get
> > my Google OpenID's to work there, but I have others around, I'm sure.
> >
> > Ben Fulton
> >
> >
> >
> > On Tue, Oct 27, 2015 at 4:56 AM, Peter Cock <p.j.a.cock at googlemail.com>
> > wrote:
> >>
> >> Thanks Tiago & Ben,
> >>
> >> For now we're leaving the 64bit builds to Christoph Gohlke since
> >> that ensures they'll be consistent with his NumPy packages (and
> >> so far there are no official NumPy Windows 64-bit installers).
> >> But there is demand for the 32bit Windows installers :)
> >>
> >> For Appveyor there was an interesting thread on the NumPy
> >> list this summer with links to example projects using it:
> >>
> https://mail.scipy.org/pipermail/numpy-discussion/2015-March/072391.html
> >>
> >> Using AppVeyor to build our Windows installers for us seems like
> >> an interesting idea - at very least I would be pleased to have it
> >> doing continuous integration testing under Windows :)
> >>
> >> Ben's branch is currently here:
> >> https://github.com/benfulton/biopython/tree/appveyor
> >>
> >> Peter
> >>
> >> On Mon, Oct 26, 2015 at 11:24 PM, Tiago Antão <tiagoantao at gmail.com>
> >> wrote:
> >> > I currently do not have a windows machine at alk. But I do expect to
> >> > receive
> >> > a windows 10 in the next couple of weeks.
> >> >
> >> > On Oct 26, 2015 11:36 AM, "Ben Fulton" <ben at benfulton.net> wrote:
> >> >>
> >> >> Yes, I'll take a look at that. I used Appveyor to build Windows 32
> and
> >> >> 64-bit installers with Python 3.5 already
> >> >> (https://ci.appveyor.com/project/benfulton/biopython/build/1.0.18)
> but
> >> >> that
> >> >> wasn't with the 1.66 code.
> >> >>
> >> >> Ben Fulton
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.open-bio.org/pipermail/biopython-dev/attachments/20151028/2c0ea25f/attachment.html>