<div dir="ltr">I was able to get an AppVeyor build going. It requires a top-level file and a directory with a few configuration files in it. To get everything to build I had to make a few changes, though:<div><br></div><div>- Change the version from 1.65+ to 1.65, as the + isn't recognized by all versions</div><div>- Add "2012Server" to the list of Windows versions in which to set shell=true. (With that change I do wonder if there is any OS where shell needs to be false at all)</div><div>- Change setup.py to import setup from setuptools rather than distutils.core. This is required to get bdist_wheel as a setup command. I'm not sure if there are any issues with importing just this one function from setuptools and the others from distutils.</div><div><br></div><div>After that I did get several wheels to build, though. If someone wants to associate an Appveyor account with the Biopython Github account, I'd be happy to submit a pull request with these changes.</div><div><br></div><div>Ben Fulton</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 24, 2015 at 5:23 PM, 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"><div dir="ltr">Hello all,<div><br></div><div>It seems there are some changes ahead with PyPI, the</div><div>Python Package Index which is one of the best ways to</div><div>distribute Python packages and deal with their dependencies.</div><div><br></div><div>Of the options below, I lean towards moving / mirroring</div><div>all our existing releases to PyPI - in part as in the long</div><div>term that means one less thing to administer on the OBF</div><div>volunteer maintained web server.</div><div><br></div><div>Does anyone here have first hand experience of this</div><div>migration?<br></div><div><br></div><div><div>On a related point, we ought to look at providing the</div><div>Windows pre-compiled Biopython as wheel format. e.g.</div></div><div><a href="https://packaging.python.org/en/latest/appveyor/" target="_blank">https://packaging.python.org/en/latest/appveyor/</a><br></div><div><br></div><div>Thanks,</div><div><br></div><div>Peter</div><div><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Donald Stufft</b> <span dir="ltr"><<a href="mailto:donald@python.org" target="_blank">donald@python.org</a>></span><br>Date: Thu, Sep 24, 2015 at 8:16 PM<br>Subject: Important notice about your projects on PyPI<br>To: <a href="mailto:p.j.a.cock@googlemail.com" target="_blank">p.j.a.cock@googlemail.com</a><br><br><br>Hello peterjc!<br>
<br>
Please forgive me if this is the second (or third... I swear I tested it fully<br>
this time!) copy you've received of this message, a bug has forced us to<br>
resend the batch. Sorry for the extra noise D:<br>
<br>
This is an automated message because you are listed as an owner or maintainer<br>
of the following project on PyPI:<br>
<br>
* biopython<br>
<br>
Due to the acceptance of PEP 470, PyPI is going to remove the ability for a<br>
project to host it's files somewhere other than on PyPI, but still have PyPI<br>
instruct installers (such as pip) to go and fetch this file automatically.<br>
PEP 470 removes this feature and any project relying on it will need to either<br>
be moved to hosting on PyPI or, if you wish to continue to host it externally,<br>
you'll need to host your own repository and instruct your users to add that<br>
repository to their installer. To give you time to adjust, this change will not<br>
happen for 3 months, but after that 3 month deadline has expired, unless you<br>
act some or all of the files for the above projects will no longer be found by<br>
automated installers.<br>
<br>
If you wish, there is a script available at <a href="https://pypi.python.org/pypi/pep470" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/pep470</a><br>
which can be used to automatically migrate any of the affected files for your<br>
own projects to PyPI.<br>
<br>
If you wish to continue to host your files yourself instead of uploading them<br>
to PyPI, then you should follow the instructions at<br>
<a href="https://packaging.python.org/en/latest/self_hosted_repository/" rel="noreferrer" target="_blank">https://packaging.python.org/en/latest/self_hosted_repository/</a>.<br>
<br>
If you have any questions about the migration, please first check the FAQ at<br>
<a href="https://github.com/pypa/pep470/wiki/Frequently-Asked-Questions" rel="noreferrer" target="_blank">https://github.com/pypa/pep470/wiki/Frequently-Asked-Questions</a> which will be<br>
updated with any questions and answers that come up during the migration<br>
process.<br>
<br>
Here are all of the links that we've discovered for each project of yours which<br>
are not currently hosted on PyPI:<br>
<br>
biopython:<br>
<a href="http://biopython.org/DIST/biopython-1.00a3.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.00a3.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.00a4.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.00a4.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.10.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.10.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.20.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.20.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.21.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.21.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.22.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.22.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.23.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.23.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.24.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.24.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.30.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.30.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.40b.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.40b.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.41.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.41.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.42.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.42.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.43.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.43.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.44.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.44.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.45.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.45.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.46.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.46.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.47.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.47.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.48.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.48.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.49.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.49.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.49b.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.49b.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.50b.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.50b.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.51b.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.51b.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.54b.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.54b.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.55b.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.55b.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.62b.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.62b.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-1.63b.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-1.63b.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-corba-0.2.1.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-corba-0.2.1.tar.gz</a><br>
<a href="http://biopython.org/DIST/biopython-corba-0.3.0.tar.gz" rel="noreferrer" target="_blank">http://biopython.org/DIST/biopython-corba-0.3.0.tar.gz</a><br>
<br>
Thanks for your time!<br>
<span><font color="#888888"><br>
Donald Stufft<br>
PyPI Administrator</font></span></div><br></div></div>
<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></blockquote></div><br></div>