<div dir="ltr">Yes, I'll take a look at that. I used Appveyor to build Windows 32 and 64-bit installers with Python 3.5 already (<a href="https://ci.appveyor.com/project/benfulton/biopython/build/1.0.18">https://ci.appveyor.com/project/benfulton/biopython/build/1.0.18</a>) but that wasn't with the 1.66 code.<div><br></div><div>Ben Fulton</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 26, 2015 at 11:44 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">Continuing the Windows installer .exe vs .msi discussion,<br>
I was reminded on Twitter that we don't have either for<br>
Windows users running Python 3.5 yet.<br>
<br>
<a href="https://twitter.com/FranjoIvankovic/status/658654973128024064" rel="noreferrer" target="_blank">https://twitter.com/FranjoIvankovic/status/658654973128024064</a><br>
<a href="https://twitter.com/Biopython/status/658667763729342464" rel="noreferrer" target="_blank">https://twitter.com/Biopython/status/658667763729342464</a><br>
<br>
Python 3.5 does not support Windows XP, which is past<br>
the Microsoft end of life. My own Windows XP machine<br>
is essentially only still in use for building the Biopython<br>
installers and as a buildbot slave for testing.<br>
<br>
We need someone with a more recent Windows machine<br>
and all the relevant compilers setup to volunteer to build<br>
an installer for Python 3.5 (and ideally the older versions<br>
too).<br>
<br>
Ben or Tiago - this this something you could tackle?<br>
<br>
Thanks,<br>
<br>
Peter<br>
<br>
On Fri, Oct 23, 2015 at 5:32 PM, Peter Cock <<a href="mailto:p.j.a.cock@googlemail.com">p.j.a.cock@googlemail.com</a>> wrote:<br>
> Hi Ben,<br>
><br>
> I did a little reading about how to make an MSI file. Specifically<br>
> <a href="https://docs.python.org/2/distutils/builtdist.html" rel="noreferrer" target="_blank">https://docs.python.org/2/distutils/builtdist.html</a> suggested:<br>
><br>
> python setup.py bdist_msi<br>
><br>
> This worked fine on my old Windows XP machine for:<br>
><br>
> C:\Python33\python setup.py bdist_wininst<br>
> C:\Python34\python setup.py bdist_wininst<br>
><br>
> However Python 2.6 and 2.7 fail somewhat cryptically giving<br>
> me an incomplete MSI file:<br>
><br>
>> C:\Python27\python setup.py bdist_wininst<br>
> ...<br>
> running install_egg_info<br>
> Writing build\bdist.win32\msi\Lib\site-packages\biopython-1.66-py2.7.egg-info<br>
> Traceback (most recent call last):<br>
> File "setup.py", line 493, in <module><br>
> setup(**setup_args)<br>
> File "c:\python27\lib\distutils\core.py", line 152, in setup<br>
> dist.run_commands()<br>
> File "c:\python27\lib\distutils\dist.py", line 953, in run_commands<br>
> self.run_command(cmd)<br>
> File "c:\python27\lib\distutils\dist.py", line 972, in run_command<br>
> cmd_obj.run()<br>
> File "c:\python27\lib\distutils\command\bdist_msi.py", line 255, in run<br>
> self.add_files()<br>
> File "c:\python27\lib\distutils\command\bdist_msi.py", line 308, in add_files<br>
> key = seen[afile] = dir.add_file(file)<br>
> File "c:\python27\lib\msilib\__init__.py", line 340, in add_file<br>
> short = self.make_short(file)<br>
> File "c:\python27\lib\msilib\__init__.py", line 299, in make_short<br>
> assert file not in self.short_names<br>
> AssertionError<br>
><br>
> From a little debugging this was a bug in the standard library<br>
> where Bio/Entrez/DTDs/MMDB.dtd and MMDB.mod.dtd are<br>
> both mapped to the upper case short name MMDB.DTD, without<br>
> noticing the middle part of the filename. i.e.<br>
><br>
> <a href="http://bugs.python.org/issue1128" rel="noreferrer" target="_blank">http://bugs.python.org/issue1128</a><br>
><br>
> This should have been fixed as part of:<br>
><br>
> <a href="http://bugs.python.org/issue7639" rel="noreferrer" target="_blank">http://bugs.python.org/issue7639</a><br>
><br>
> It looks like I need to update to Python 2.7.2 or later for the fix, but<br>
> it may never have been addressed in an official Python 2.6.x<br>
> release (I could backport this if required).<br>
><br>
> Leaving those problematic builds aside, do you think I should<br>
> upload these 32-bit MSI files for Biopython 1.66?<br>
><br>
> Peter<br>
><br>
> On Thu, Oct 22, 2015 at 9:58 PM, Peter Cock <<a href="mailto:p.j.a.cock@googlemail.com">p.j.a.cock@googlemail.com</a>> wrote:<br>
>> Thanks Ben,<br>
>><br>
>> This has all changed since back when I used Windows - you're<br>
>> perhaps in a good position to take charge of Biopython on Windows?<br>
>><br>
>> Peter<br>
>><br>
>> On Thu, Oct 22, 2015 at 7:23 PM, Ben Fulton <<a href="mailto:ben@benfulton.net">ben@benfulton.net</a>> wrote:<br>
>>> I installed the Python 2.7 version successfully on Windows. Building an MSI<br>
>>> might be advisable instead of an exe, though; on Windows 8 I get:<br>
>>><br>
>>> "Windows protected your PC. Windows SmartScreen prevented an unrecognized<br>
>>> app from starting. Running this app might put your PC at risk"<br>
>>><br>
>>> To install it you have to click "More info", which tells you that the<br>
>>> publisher is unknown and has a button that says "Run anyway".<br>
>>><br>
</blockquote></div><br></div>