FAQ

On 7 September 2015 at 11:22, Ryan Gonzalez wrote:
On September 6, 2015 12:33:29 PM CDT, "Sven R. Kunze" wrote:
really insightful. Viewing this from a different angle, packaging your
own distribution is actually a waste of time. It is a tedious,
error-prone task involving no creativity whatsoever. Developers on the
other hand are actually people with very little time and a lot of
creativity at hand which should spend better. The logical conclusion
would be that PyPI should build wheels for the developers for every
python/platform combination necessary.
You can already do this with CI services. I wrote a post about doing that with AppVeyor:

http://kirbyfan64.github.io/posts/using-appveyor-to-distribute-python-wheels.html

but the idea behind it should apply easily to Travis and others. In reality, you're probably using a CI service to run your tests anyway, so it might as well build your wheels, too!

Right, Appveyor also has the most well-defined CI instructions on
packaging.python.org:
https://packaging.python.org/en/latest/appveyor.html


It doesn't do auto-upload, as many projects only release occasionally
rather than for every commit. However, it may be desirable to go into
more detail about how to do that, if you'd be interested in sending a
PR based on your post.


Cheers,
Nick.


--
Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 9 of 16 | next ›
Discussion Overview
grouppython-ideas @
categoriespython
postedSep 6, '15 at 5:33p
activeSep 10, '15 at 5:46p
posts16
users10
websitepython.org

People

Translate

site design / logo © 2017 Grokbase