[Numpy-discussion] Refactor fork uses the ./configure, make, make install process.

Charles R Harris charlesr.harris at gmail.com
Sat Dec 4 16:01:03 EST 2010

On Sat, Dec 4, 2010 at 1:45 PM, Pauli Virtanen <pav at iki.fi> wrote:

> On Sat, 04 Dec 2010 14:24:49 -0600, Ilan Schnell wrote:
> > I'm not sure how reasonable it would be to move only libndarray into the
> > master, because I've been working on EPD for the last couple of week.
> > But Jason will know how complete libndarray is.
> The main question is whether moving it will make things easier or more
> difficult, I think. It's one tree more to keep track of.
> In any case, it would be a first part in the merge, and it would split
> the hunk of changes into two parts.
That would be a good thing IMHO. It would also bring a bit more numpy
reality to the refactor and since we are implicitly relying on it for the
next release sometime next spring the closer to reality it gets the better.

>    ***
> Technically, the move could be done like this, so that merge tracking
> still works:
>           --------refactor--------------- new-refactor
>          /                            /
>         /--------libndarray----------x
>        /                              \
>   start---------------------- master----- new-master
Looks good to me.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20101204/701a97d9/attachment.html>

More information about the NumPy-Discussion mailing list