RE: [IronPython] RE: Numpy port

2005-08-31 Thread J. Merrill
Oh good -- we can program in "pithy" !!! At 07:11 PM 8/31/2005, Keith J. Farmer wrote >It's okay to interchange 'i' and 'y' .. so you can go through each combination >of i/y that occurs in each part. >___ > >From: [EMAIL PROTECTED] on behalf of Thane >Sent: Wed 8/31/20

RE: [IronPython] RE: Numpy port

2005-08-31 Thread Keith J. Farmer
It's okay to interchange 'i' and 'y' .. so you can go through each combination of i/y that occurs in each part. From: [EMAIL PROTECTED] on behalf of Thane Sent: Wed 8/31/2005 2:00 PM To: 'Discussion of IronPython' Subject: RE: [IronPython] RE: Numpy port essen

RE: [IronPython] RE: Numpy port

2005-08-31 Thread Thane
essential_parts = "py,pyth,python".split(',') other_parts = "net,i,ir,iron,fe,ferrous,-anything-but-sharp-".split(',') for part1 in essential_parts: for part2 in other_parts: print part1+part2 print part2+part1 (Doesn't include "Pyronic" which I

RE: [IronPython] RE: Numpy port

2005-08-31 Thread Keith J. Farmer
"Pynet".. then instead of "Pythonistas", we could call ourselves "goobers". (that's okay..) From: [EMAIL PROTECTED] on behalf of Anthony Tarlano Sent: Wed 8/31/2005 11:02 AM To: Discussion of IronPython Subject: Re: [IronPython] RE: Numpy port I was thinking a

Re: [IronPython] RE: Numpy port

2005-08-31 Thread Anthony Tarlano
I was thinking about the name thing again and I really like: pythonet   ;-) (sorry if this brings an onslaught of new naming messages)On 8/31/05, Ken Manheimer <[EMAIL PROTECTED] > wrote:just incidentally:On 8/27/05, Thane < [EMAIL PROTECTED]> wrote:> [...]> I think that "numpy" is the import na

Re: [IronPython] RE: Numpy port

2005-08-31 Thread Ken Manheimer
just incidentally: On 8/27/05, Thane <[EMAIL PROTECTED]> wrote: > [...] > I think that "numpy" is the import name for the "Numerical" library > originally created by Paul Dubois. it's worth noting that it was our jim hugunin who originated numerical python. from http://www.pfdubois.com/numpy/ht

RE: [IronPython] RE: Numpy port

2005-08-31 Thread Morgan Martinet
> I wouldn't call the FORTRAN "legacy code". People are still using BLAS > and such because the FORTRAN code performs better. These routines have > been rewritten many times in C, C++, and Java and people still use the > FORTRAN simply because it does a better job. Numerical solutions are > wha

RE: [IronPython] RE: Numpy port

2005-08-31 Thread Michael Gogins
I wouldn't call the FORTRAN "legacy code". People are still using BLAS and such because the FORTRAN code performs better. These routines have been rewritten many times in C, C++, and Java and people still use the FORTRAN simply because it does a better job. Numerical solutions are what FORTRAN w

Re: [IronPython] RE: Numpy port

2005-08-31 Thread Paul Barrett
On 8/31/05, Jeffrey Sax <[EMAIL PROTECTED]> wrote: I had a look at this a few months ago. Both numarray and Numeric use anamorphous char array for storage. A simple wrapper would mean a lot ofunmanaged memory moving around... not a desirable situation. True. It seems to me that a rewrite using gen

RE: [IronPython] RE: Numpy port

2005-08-31 Thread Jeffrey Sax
I had a look at this a few months ago. Both numarray and Numeric use an amorphous char array for storage. A simple wrapper would mean a lot of unmanaged memory moving around... not a desirable situation. It seems to me that a rewrite using generics is most appropriate. The CLR generics should tak