I don't know if it has been mentioned before, but Travis already provides a way to automatically package and upload sdists and wheels to PyPI: https://docs.travis-ci.com/user/deployment/pypi/ I've been using it myself in many projects and it has worked quite well. Granted, I haven't had to deal with binary wheels yet, but I think Travis should be able to handle creation of macOS and manylinux1 wheels. 03.11.2016, 22:07, Nathaniel Smith kirjoitti:
I think we're drifting pretty far off topic here... IIRC the original discussion was about whether the travis-ci infrastructure could be suborned to provide an sdist->wheel autobuilding service for pypi. (Answer: maybe, though it would be pretty awkward, and no one seems to be jumping up to make it happen.)
On Nov 3, 2016 11:28 AM, "Barry Warsaw"
mailto:barry@python.org> wrote: On Nov 03, 2016, at 11:08 AM, Glyph Lefkowitz wrote:
>I think phrasing this in terms of "perfect" and "good enough" presents a >highly misleading framing. Examined in this fashion, of course we may >reluctantly use the "good enough" option, but don't we want the best option?
What are the criteria for "best"?
I'm not saying don't use Travis, I'm just trying to express that there are technical limitations, which is almost definitely true of any CI infrastructure. If those limitations don't affect your project, great, go for it!
Cheers, -Barry
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org mailto:Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig https://mail.python.org/mailman/listinfo/distutils-sig
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig