<div dir="ltr">I installed the Python 2.7 version successfully on Windows. Building an MSI might be advisable instead of an exe, though; on Windows 8 I get:<div><br></div><div>"Windows protected your PC. Windows SmartScreen prevented an unrecognized app from starting. Running this app might put your PC at risk"</div><div><br></div><div>To install it you have to click "More info", which tells you that the publisher is unknown and has a button that says "Run anyway".</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 22, 2015 at 5:34 AM, Peter Cock <span dir="ltr"><<a href="mailto:p.j.a.cock@googlemail.com" target="_blank">p.j.a.cock@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Wed, Oct 21, 2015 at 6:14 PM, Peter Cock <<a href="mailto:p.j.a.cock@googlemail.com">p.j.a.cock@googlemail.com</a>> wrote:<br>
</span><span class="">> Hi all,<br>
><br>
> Sanity testing of these provisional source bundles and binaries already on<br>
> <a href="http://biopython.org/DIST/" rel="noreferrer" target="_blank">http://biopython.org/DIST/</a> would be appreciated, especially during the next<br>
> few hours (during which time I will draft the release announcement and<br>
> have dinner), and prior to the push to PyPI:<br>
><br>
> 2f09afb0a7740a70f64b6d10dfc2582b biopython-1.66.tar.gz<br>
> 4344c2e7b91deb47f9ae2ebf7ad1e375 biopython-1.66.zip<br>
> 192bc8a70fe098e5eae71fc3ad38e3fd biopython-1.66.win32-py2.6.exe<br>
> 6e4bf2b9eb9533ebd6930df6b506db51 biopython-1.66.win32-py2.7.exe<br>
> fa7a6010b7ecce7fdd8fa614a3f5845e biopython-1.66.win32-py3.3.exe<br>
> c985a3477032314c1ec78e8ada916371 biopython-1.66.win32-py3.4.exe<br>
><br>
> These should match this commit (not tagged yet):<br>
><br>
> <a href="https://github.com/biopython/biopython/commit/c06a3066d858c4818cc6b4bf7e8d776bb9473a63" rel="noreferrer" target="_blank">https://github.com/biopython/biopython/commit/c06a3066d858c4818cc6b4bf7e8d776bb9473a63</a><br>
<br>
</span>Update to PyPI done:<br>
<br>
<a href="https://pypi.python.org/pypi/biopython/1.66" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/biopython/1.66</a><br>
<br>
Interestingly this seem to insist on rebuilding the tar-ball, which<br>
means the tar ball now up on PyPI has a different md5sum:<br>
<br>
d3f4c14e5cba3dfd354d0e0013bc350f dist/biopython-1.66.tar.gz<br>
<br>
I presume this is down to containing different date stamp(s).<br>
<br>
If we start to advertise the expected md5 checksums in future, this may<br>
mean revising our release process slightly... not that I have followed<br>
<a href="http://biopython.org/wiki/Building_a_release" rel="noreferrer" target="_blank">http://biopython.org/wiki/Building_a_release</a> exactly by delaying the<br>
PyPI release until I'd had a third party confirm the downloads looked<br>
fine.<br>
<div class="HOEnZb"><div class="h5"><br>
Peter<br>
_______________________________________________<br>
Biopython-dev mailing list<br>
<a href="mailto:Biopython-dev@mailman.open-bio.org">Biopython-dev@mailman.open-bio.org</a><br>
<a href="http://mailman.open-bio.org/mailman/listinfo/biopython-dev" rel="noreferrer" target="_blank">http://mailman.open-bio.org/mailman/listinfo/biopython-dev</a><br>
</div></div></blockquote></div><br></div>