On Mon, Jan 11, 2016 at 6:25 PM, Chris Barker <chris.bar...@noaa.gov> wrote:
> On Fri, Jan 8, 2016 at 7:13 PM, Nathaniel Smith <n...@pobox.com> wrote: > >> > that this would potentially be able to let packages like numpy serve >> their >> > linux >> > users better without risking too much junk being uploaded to PyPI. >> >> That will never fly. But like Matthew says, I think we can probably >> get them to accept a PEP saying "here's a new well-specified platform >> tag that means that this wheel works on all linux systems meet the >> following list of criteria: ...", and then allow that new platform tag >> onto PyPI. >> > > The second step is a trick though -- how does pip know, when being run on > a client, that the system meets those requirements? Do we put a bunch of > code in that checks for those libs, etc??? > You could make that option an opt-in at first, and gradually autodetect it for the main distros. > > If we get all that worked out, we still haven't made any progress toward > the non-standard libs that aren't python. This is the big "scipy problem" > -- fortran, BLAS, hdf, ad infinitum. > > I argued for years that we could build binary wheels that hold each of > these, and other python packages could depend on them, but pypa never > seemed to like that idea. > I don't think that's an accurate statement. There are issues to solve around this, but I did not encounter push back, either on the ML or face to face w/ various pypa members at Pycon, etc... There may be push backs for a particular detail, but making "pip install scipy" or "pip install matplotlib" a reality on every platform is something everybody agrees o > >
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion
