> On Dec 14, 2016, at 9:41 AM, Chris Barker <chris.bar...@noaa.gov> wrote:
>
> As pointed out by others, there are external groups doing "curating".
> conda-forge is one such project, so I'll comment from that perspective:
>
>
> It's difficult because the definition of compatibility is highly dependent on
> the consumer's environment. For example, C extension compatibility will
> depend on the version of libraries available on the platform versions you care
> about.
>
> Indeed -- which is why Anaconda and conda-forge are built on conda rather
> than pip -- it is designed to handle these issues.
>
> However with the many linux effort, and some efforts to kludge C libs into
> binary wheels, pypi may just be able to handle more of these issues -- so
> curating may have it's advantages.
I think it's unfair to describe these efforts as a "kludge"; many of the tools
developed for manylinux1 et. al. are actually pretty sophisticated tooling with
a mature ecosystem approach to library bundling. Personally I have noticed a
_massive_ reduction in the support overhead involved in getting new users spun
up in the present Python packaging ecosystem. Due to the availability of
cross-platform wheels, it's possible to do a LOT more python development
without a C compiler than it used to be.
-glyph
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
