On 10/25/20 5:39 PM, Dustin Spicuzza wrote:
Sorry for not being clear, when I was discussing modifications to scipy
I was referring to the specific use case of cross-compilation. The goal
is that existing native builds would not break backwards compatibility.
To that end, there's a package redi
On 10/25/20 11:39 AM, Dustin Spicuzza wrote:
> On 10/25/20 5:23 AM, Matti Picus wrote:
>> On 10/25/20 10:46 AM, Dustin Spicuzza wrote:
>>> I took a first stab at it, and... surprise, surprise, there were a few
>>> more warts than I had originally expected in my initial survey. The
>>> biggest unex
On 10/25/20 5:23 AM, Matti Picus wrote:
>
> On 10/25/20 10:46 AM, Dustin Spicuzza wrote:
>> I took a first stab at it, and... surprise, surprise, there were a few
>> more warts than I had originally expected in my initial survey. The
>> biggest unexpected result is that numpy.f2py would need to als
NumPy could take an explicit runtime dependency on numpy-distutils so that
the code would be technically in a different repo bit would always be
available through NumPy. Eventually this could be removed as a runtime
dependency.
Kevin
On Sun, Oct 25, 2020, 09:23 Matti Picus wrote:
>
> On 10/25/
On 10/25/20 10:46 AM, Dustin Spicuzza wrote:
I took a first stab at it, and... surprise, surprise, there were a few
more warts than I had originally expected in my initial survey. The
biggest unexpected result is that numpy.f2py would need to also be a
toplevel package. I did get the refactor c
On 10/24/20 2:59 PM, Dustin Spicuzza wrote:
> Since this initial feedback seems mostly positive, I'll go ahead and
> take a stab at refactoring it and make a PR potentially this weekend.
> It should be fairly straightforward.
>
> Dustin
I took a first stab at it, and... surprise, surprise, ther
