On Jan 23, 2014, at 4:17 PM, Oscar Benjamin <oscar.j.benja...@gmail.com> wrote:
> On 23 January 2014 23:58, Nick Coghlan <ncogh...@gmail.com> wrote: >> >> I really think that's our best near term workaround - still room for >> improvement, but " pip install numpy assumes SSE2" is a much better >> situation than "pip install numpy doesn't work on Windows". > > Is it? Do you have any idea what proportion of (the relevant) people > would be using Windows with hardware that doesn't support SSE2? I feel > confident that it's less than 10% but I don't know how to justify a > tighter bound than that. > > You need to bear in mind that people currently have a variety of ways > to install numpy on Windows that do work already without limitations > on CPU instruction set. Most numpy users will not get any immediate > benefit from the fact that "it works using pip" rather than "it works > using the .exe installer" (or any of a number of other options). It's > the unfortunate end users and the numpy folks who would have to pick > up the pieces if/when the SSE2 assumption fails. > This all sounds very similar to the issues with Linux binary wheels and varying system ABIs. Should probably keep in mind for any solution that might apply to both. --Noah
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
