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

2010-12-07 Thread Charles R Harris
On Tue, Dec 7, 2010 at 5:36 PM, Ralf Gommers wrote: > > > On Wed, Dec 8, 2010 at 2:57 AM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Tue, Dec 7, 2010 at 11:34 AM, Jason McCampbell < >> jmccampb...@enthought.com> wrote: >> >>> Sorry for the late reply... I missed this thre

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

2010-12-07 Thread Ralf Gommers
On Wed, Dec 8, 2010 at 2:57 AM, Charles R Harris wrote: > > > On Tue, Dec 7, 2010 at 11:34 AM, Jason McCampbell < > jmccampb...@enthought.com> wrote: > >> Sorry for the late reply... I missed this thread. Thanks to Ilan for >> pointing it out. A variety of comments below... >> >> On Sat, Dec 4,

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

2010-12-07 Thread Charles R Harris
On Tue, Dec 7, 2010 at 11:34 AM, Jason McCampbell wrote: > Sorry for the late reply... I missed this thread. Thanks to Ilan for > pointing it out. A variety of comments below... > > On Sat, Dec 4, 2010 at 10:20 AM, Charles R Harris< > charlesr.har...@gmail.com> wrote: > >> Just wondering if thi

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

2010-12-07 Thread Jason McCampbell
Sorry for the late reply... I missed this thread. Thanks to Ilan for pointing it out. A variety of comments below... On Sat, Dec 4, 2010 at 10:20 AM, Charles R Harris wrote: > Just wondering if this is temporary or the intention is to change the > build process? I also note that the *.h files i

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

2010-12-05 Thread David
On 12/05/2010 05:57 AM, Dag Sverre Seljebotn wrote: > On 12/04/2010 09:11 PM, Charles R Harris wrote: >> >> >> On Sat, Dec 4, 2010 at 12:59 PM, Ilan Schnell > > wrote: >> >> Yes, numpy-refactor builds of top of libndarray. The whole point >> was that the libnd

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

2010-12-04 Thread Mark Wiebe
On Sat, Dec 4, 2010 at 12:45 PM, Pauli Virtanen wrote: > > Technically, the move could be done like this, so that merge tracking > still works: > > refactor--- new-refactor > // > /libndarray--x >/

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

2010-12-04 Thread Charles R Harris
On Sat, Dec 4, 2010 at 1:45 PM, Pauli Virtanen 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 comple

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

2010-12-04 Thread Dag Sverre Seljebotn
On 12/04/2010 09:11 PM, Charles R Harris wrote: On Sat, Dec 4, 2010 at 12:59 PM, Ilan Schnell > wrote: Yes, numpy-refactor builds of top of libndarray. The whole point was that the libndarray is independent of the interface, i.e. the CPython or the

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

2010-12-04 Thread Pauli Virtanen
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

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

2010-12-04 Thread Ilan Schnell
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. - Ilan On Sat, Dec 4, 2010 at 2:19 PM, Charles R Harris wrote: > Would it unreasonable to move the libnd

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

2010-12-04 Thread Charles R Harris
On Sat, Dec 4, 2010 at 12:52 PM, Pauli Virtanen wrote: > On Sat, 04 Dec 2010 12:21:15 -0700, Charles R Harris wrote: > [clip] > > So does numpy currently build on top of libndarray or is that something > > for the future also? > [clip] > > It does. If you look how it works, most of the heavy lift

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

2010-12-04 Thread Charles R Harris
On Sat, Dec 4, 2010 at 12:59 PM, Ilan Schnell wrote: > Yes, numpy-refactor builds of top of libndarray. The whole point > was that the libndarray is independent of the interface, i.e. the > CPython or the IronPython interface, and possibly other (Jython) > in the future. > Looking at different bu

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

2010-12-04 Thread Ilan Schnell
Yes, numpy-refactor builds of top of libndarray. The whole point was that the libndarray is independent of the interface, i.e. the CPython or the IronPython interface, and possibly other (Jython) in the future. Looking at different building/packaging solutions for libndarray, autoconf make things

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

2010-12-04 Thread Pauli Virtanen
On Sat, 04 Dec 2010 12:21:15 -0700, Charles R Harris wrote: [clip] > So does numpy currently build on top of libndarray or is that something > for the future also? [clip] It does. If you look how it works, most of the heavy lifting has been moved there, leaving the multiarray module mostly as Pyt

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

2010-12-04 Thread Charles R Harris
On Sat, Dec 4, 2010 at 12:07 PM, Ilan Schnell wrote: > Hello Charles, > > it was indeed the intention to change the build process of the core > libndarray to use autoconf. I've tested it on Linux, Mac, Solaris, and > it works very well. libndarray is really a separate project, which only > resid

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

2010-12-04 Thread Ilan Schnell
Hello Charles, it was indeed the intention to change the build process of the core libndarray to use autoconf. I've tested it on Linux, Mac, Solaris, and it works very well. libndarray is really a separate project, which only resides for current development inside the numpy project. The point i

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

2010-12-04 Thread Charles R Harris
Hi Jason, Just wondering if this is temporary or the intention is to change the build process? I also note that the *.h files in libndarray are not complete and a *lot* of trailing whitespace has crept into the files. Chuck ___ NumPy-Discussion mailing