Re: Using NumPy/SciPy/scikit-learn approach to building wheels
Peter Cock <[email protected]> Wed, 19 Jul 2017 12:27:59 +0100
| Newsgroups | gmane.comp.python.bio.devel |
|---|---|
| Message-ID | <CAKVJ-_4P94dQ3F0by6ceKNp3HtGyJMxQbC2qfh32gT0+5dinzQ@mail.gmail.com> |
Hello all, It turns out to be quite easy to extend the new build system to make windows EXE and MSI installers (although not to test them), but something in the setup refused to upload the MSI files to Rackspace: https://github.com/matthew-brett/multibuild/issues/39 For now I will leave the EXE installers here: http://a365fff413fe338398b6-1c8a9b3114517dc5fe17b7c3f8c63a43.r19.cf2.rackcdn.com/ If there is interest, we could put them up on Biopython.org as in previous releases (and I'm sure with a little more investigation this could be done for the MSI versions as well). For now, let's see what feedback we get from Windows users with installing via pip. Peter The checksums for reference: $ md5sum biopython-1.70*.exe 65b75b4fc26624921ad50e7995e8901c biopython-1.70.win32-py2.7.exe 366376cc9767e5446dbad0c1b9d87f3a biopython-1.70.win32-py3.4.exe 177259d083c8281e77e19062a6b18c65 biopython-1.70.win32-py3.5.exe 7130f29de2ee6ac12f63b0ed16b0aef2 biopython-1.70.win32-py3.6.exe d0f767028b19ed1333834f18020dfd78 biopython-1.70.win-amd64-py2.7.exe 7e4e57461823fb5ea72a7cb50c63992b biopython-1.70.win-amd64-py3.4.exe 6552735f126753989c6ec41a19764556 biopython-1.70.win-amd64-py3.5.exe e2523f8bca07969107137ba62876eb03 biopython-1.70.win-amd64-py3.6.exe $ shasum -a 256 biopython-1.70*.exe 90a302f496738b60918e529183d318cc1fb61191677314d8453eafa78858fbac biopython-1.70.win32-py2.7.exe 10a1c412f8e541871539e1678d45eb5a4aa9c5231261624f52998d595469d7ad biopython-1.70.win32-py3.4.exe d526dbbb848a2e85fcdf2758010507ee02f3a99cee0a1c23a599d32d3976c66b biopython-1.70.win32-py3.5.exe affb77343b6c7b08710b35fb9b9b0011992a9c456a4a95183ecf7888c548eed9 biopython-1.70.win32-py3.6.exe ed7aa36f63f6b48f0cade74dfdd7bc4ab46d03a7403204a83142988d5b37f3b3 biopython-1.70.win-amd64-py2.7.exe 7e6fa412fde1500adb3f53941d037865e4f9a4ce76355dfae88d8549efef2a72 biopython-1.70.win-amd64-py3.4.exe 7afc39455893c379cfbe6a6839ae9bf918910d6b5fbdd56a63992fd5b91c6209 biopython-1.70.win-amd64-py3.5.exe 26685dc0e0212086791244efb9961f1d9eebc2269c4098c8ab007f36baf3bf38 biopython-1.70.win-amd64-py3.6.exe On Tue, Jul 18, 2017 at 2:29 PM, Peter Cock <[email protected]> wrote: > Perfect, thank you Markus. > > With the assistance of a colleague we could test the 32-bit > Python 2.7 and 3.6 wheels. > > The hardest part was finding pip in order to run the command. > > For Python 2.7 we first had to upgrade Python as the early > point releases did not include it (this is simpler than > bootstrapping a pip installation), then it was available as: > > C:\Python27\Scripts\pip > > (Optionally including the .exe extension). > > For Python 3.6, it seems the default installation folder was > a per-user app-data folder which is harder to describe... > > In neither case was pip on the path - so we're going to have > to give slightly more guidance for Windows installation from > a wheel. > > My colleague is of the view that continuing to offer EXE or MSI > installers does significantly lower the barrier of entry - although > as far as I can tell this would limit you to NumPy 1.10.2 (from > December 2015): > > https://sourceforge.net/projects/numpy/files/NumPy/1.10.2/ > > For now I will get the wheels uploaded to PyPI... > > Thanks all, > > Peter