[Distutils] Current Python packaging status (from my point of view)

[Chris Barker]

On Tue, Nov 1, 2016 at 5:19 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:

> It isn't that simple, as what you really want to automate is the
> *release process*, where you upload an sdist, and the wheels *just
> happen* for:
>
> - the Python versions you want to support (e.g 2.7, 3.4, 3.5)
> - the platforms you want to support (typically x86_64 for Windows, Mac
> OS X, manylinux1, and maybe 32 bit Windows as well)
>

indeed -- do take a look at conda-forge, they've got all that working.

and while it ultimately calls "conda build this_thing", it wouldn't be hard
to make that a call to build a wheel instead.


> Adding a new Python release or a new platform to the build
> configuration is currently an activity that requires per-project work
> when in theory a build service could just add it automatically based
> on when new releases happen.


hmm -- maybe we could leverage gitHub, like conda-forge does -- Warehouse
would actually push to a repo on gitHub that would then trigger the CI
builds -- though the sure seems cleaner for Warehouse to call teh CIs
directly.



>
>
-- 

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/distutils-sig/attachments/20161101/f11483f3/attachment.html>