On Thu, May 26, 2022 at 3:45 AM Matti Picus <matti.pi...@gmail.com> wrote:
> On 26/5/22 05:40, Aaron Meurer wrote: > > >> We cannot do that (yet, at least). Failing to publish wheels for a > supported Python version on a major OS is far worse than dropping support > completely. This will remain true until the time that Pip starts defaulting > to wheels-only and never picks the sdist if there's an older release for > that platform + Python combo. > > sounds like if even the latest version doesn't support a given CPython > > version (and has CPython-versioned wheels), then pip installing it > > will fail. Is that correct? > > > > No. The problem is that if we do not provide binary wheels, pip > installing Numpy will not fail. It will try to build from source. Even > if this painfully and slowly succeeds, it means the user probably did > not get the BLAS support they thought they were going to get. The > situation for SciPy is similar but worse: it takes forever to build, and > will probably likewise fail to build properly. > If Python version 3.X isn't supported, and that non-support means it actually doesn't work, then it will fail. That is unless pip is smart enough to install the most recent version of NumPy that does support that version of Python (which would have wheels). Ralf made it sound like this is what would happen, but doesn't pip have python_requires to avoid this? Aaron Meurer > > Matti > > _______________________________________________ > NumPy-Discussion mailing list -- numpy-discussion@python.org > To unsubscribe send an email to numpy-discussion-le...@python.org > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > Member address: asmeu...@gmail.com >
_______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
