Re: [Numpy-discussion] genfromtxt view with object dtype

On Wed, Feb 4, 2009 at 8:51 PM, Pierre GM wrote: > OK, Brent, try r6341. > I fixed genfromtxt for cases like yours (explicit dtype involving a > np.object). > Note that the fix won't work if the dtype is nested and involves > np.objects (as we would hit the pb of renaming fields we observed...). >

Re: [Numpy-discussion] genfromtxt view with object dtype

OK, Brent, try r6341. I fixed genfromtxt for cases like yours (explicit dtype involving a np.object). Note that the fix won't work if the dtype is nested and involves np.objects (as we would hit the pb of renaming fields we observed...). Let me know how it goes. P. On Feb 4, 2009, at 4:03 PM,

Re: [Numpy-discussion] Numpy 1.3 release date ?

On Thu, Feb 5, 2009 at 2:48 AM, Charles R Harris wrote: > > > On Wed, Feb 4, 2009 at 10:01 AM, wrote: >> >> Scott Sinclair wrote: >> >> 2009/2/4 David Cournapeau : >> >> On Tue, Feb 3, 2009 at 11:49 PM, Pierre GM >> >> wrote: >> >>> All, >> >>> When can we expect numpy 1.3 to be released ? >> >

Re: [Numpy-discussion] Renaming a field of an object array

On Wed, Feb 4, 2009 at 2:50 PM, Pierre GM wrote: > All, > I'm a tad puzzled by the following behavior (I'm trying to correct a > bug in genfromtxt): > > I'm creating an empty structured ndarray, using np.object as dtype. > > >>> a = np.empty(1,dtype=[('',np.object)]) > array([(None,)], > dt

[Numpy-discussion] Renaming a field of an object array

All, I'm a tad puzzled by the following behavior (I'm trying to correct a bug in genfromtxt): I'm creating an empty structured ndarray, using np.object as dtype. >>> a = np.empty(1,dtype=[('',np.object)]) array([(None,)], dtype=[('f0', '|O4')]) Now, I'd like to rename the field: >>> a

Re: [Numpy-discussion] Multiplying a matrix by a vector

Simon Palmer wrote: > I have a matrix and a vector which has the same number of elements as the > matrix has rows. I want to multiply each element in a row in the matrix by > the corresponding element in the vector. >>> M = np.arange(6).reshape((2,3)) >>> M array([[0, 1, 2], [3, 4, 5]])

Re: [Numpy-discussion] ImportError: No module named dateutil.parser

On Wed, Feb 4, 2009 at 16:12, Pierre GM wrote: > > On Feb 4, 2009, at 3:56 PM, Robert Kern wrote: > >> No, rewrite the test to not use external libraries, please. Test the >> functionality without needing dateutils. > > OK then, should be fixed in r6340. Thank you! -- Robert Kern "I have come

Re: [Numpy-discussion] ImportError: No module named dateutil.parser

On Feb 4, 2009, at 3:56 PM, Robert Kern wrote: > > No, rewrite the test to not use external libraries, please. Test the > functionality without needing dateutils. OK then, should be fixed in r6340. ___ Numpy-discussion mailing list Numpy-discussion@sci

[Numpy-discussion] Array dtype problems

Hello, I'm having an issue with 'array' dtypes; if I do this: mydtype = numpy.dtype(('i', (4,))) arr = numpy.empty((100,), dtype=mydtype) then the array datatype shape is "absorbed" into the shape of the array. This simplifies indexing, but is really annoying as it means that the dtype doesn't

[Numpy-discussion] Multiplying a matrix by a vector

Bit of a newb question I suspect... I have a matrix and a vector which has the same number of elements as the matrix has rows. I want to multiply each element in a row in the matrix by the corresponding element in the vector. I can obviously do this with a loop, but am guessing there is a more

Re: [Numpy-discussion] genfromtxt view with object dtype

On Wed, Feb 4, 2009 at 9:36 AM, Pierre GM wrote: > > On Feb 4, 2009, at 12:09 PM, Brent Pedersen wrote: > >> hi, i am using genfromtxt, with a dtype like this: >> [('seqid', '|S24'), ('source', '|S16'), ('type', '|S16'), ('start', >> '> ' > Brent, > Please post a simple, self-contained example wit

Re: [Numpy-discussion] ImportError: No module named dateutil.parser

On Wed, Feb 4, 2009 at 14:54, Pierre GM wrote: > > On Feb 4, 2009, at 3:40 PM, Bruce Southey wrote: > >> Hi, >> I just updated to the latest SVN but I get a failure when running the >> tests due to missing dateutil.parser. Should this module exist in >> Numpy >> or just a inappropriate test? > > I

Re: [Numpy-discussion] ImportError: No module named dateutil.parser

On Feb 4, 2009, at 3:40 PM, Bruce Southey wrote: > Hi, > I just updated to the latest SVN but I get a failure when running the > tests due to missing dateutil.parser. Should this module exist in > Numpy > or just a inappropriate test? I put the corresponding tests in a try/except ImportError b

Re: [Numpy-discussion] ImportError: No module named dateutil.parser

On Wed, Feb 4, 2009 at 14:40, Bruce Southey wrote: > Hi, > I just updated to the latest SVN but I get a failure when running the > tests due to missing dateutil.parser. Should this module exist in Numpy > or just a inappropriate test? It's a bad test. -- Robert Kern "I have come to believe tha

[Numpy-discussion] ImportError: No module named dateutil.parser

Hi, I just updated to the latest SVN but I get a failure when running the tests due to missing dateutil.parser. Should this module exist in Numpy or just a inappropriate test? Bruce >>> numpy.test() Running unit tests for numpy NumPy version 1.3.0.dev6338 NumPy is installed in /usr/lib64/pytho

Re: [Numpy-discussion] porting NumPy to Python 3

Charles R Harris wrote: > > > On Wed, Feb 4, 2009 at 10:02 AM, James Watson > wrote: > > Hi Ondrej, > > To get 2to3 to run without warnings, the following files require > minor changes: > - numpy/distutils/fcompiler/intel.py > - numpy/distutils/misc

Re: [Numpy-discussion] Numpy 1.3 release date ?

On Wed, Feb 4, 2009 at 10:01 AM, wrote: > Scott Sinclair wrote: > >> 2009/2/4 David Cournapeau : > >> On Tue, Feb 3, 2009 at 11:49 PM, Pierre GM > wrote: > >>> All, > >>> When can we expect numpy 1.3 to be released ? > >> > >> I think official 2.6 support (with binaries for the platforms where

Re: [Numpy-discussion] porting NumPy to Python 3

On Wed, Feb 4, 2009 at 10:02 AM, James Watson wrote: > Hi Ondrej, > > To get 2to3 to run without warnings, the following files require minor > changes: > - numpy/distutils/fcompiler/intel.py > - numpy/distutils/misc_util.py > - numpy/distutils/command/build_src.py > - numpy/f2py/crackfortran.py >

Re: [Numpy-discussion] genfromtxt view with object dtype

On Feb 4, 2009, at 12:09 PM, Brent Pedersen wrote: > hi, i am using genfromtxt, with a dtype like this: > [('seqid', '|S24'), ('source', '|S16'), ('type', '|S16'), ('start', > ' 'http://projects.scipy.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] genfromtxt view with object dtype

hi, i am using genfromtxt, with a dtype like this: [('seqid', '|S24'), ('source', '|S16'), ('type', '|S16'), ('start', 'http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] porting NumPy to Python 3

Hi Ondrej, To get 2to3 to run without warnings, the following files require minor changes: - numpy/distutils/fcompiler/intel.py - numpy/distutils/misc_util.py - numpy/distutils/command/build_src.py - numpy/f2py/crackfortran.py - numpy/lib/function_base.py - numpy/linalg/lapack_lite/make_lite.py T

Re: [Numpy-discussion] Numpy 1.3 release date ?

Scott Sinclair wrote: >> 2009/2/4 David Cournapeau : >> On Tue, Feb 3, 2009 at 11:49 PM, Pierre GM wrote: >>> All, >>> When can we expect numpy 1.3 to be released ? >> >> I think official 2.6 support (with binaries for the platforms where we >> support binaries), x64 support and everything which

Re: [Numpy-discussion] poly1d left versus right multiplication with np numbers

On Wed, Feb 4, 2009 at 11:19 AM, Pierre GM wrote: > > On Feb 4, 2009, at 11:00 AM, josef.p...@gmail.com wrote: > >> I just had a hard to find bug in my program. poly1d treats numpy >> scalars differently than python numbers when left or right >> multiplication is used. >> >> Essentially, if the f

Re: [Numpy-discussion] poly1d left versus right multiplication with np numbers

On Feb 4, 2009, at 11:00 AM, josef.p...@gmail.com wrote: > I just had a hard to find bug in my program. poly1d treats numpy > scalars differently than python numbers when left or right > multiplication is used. > > Essentially, if the first term is the numpy scalar, multiplied by a > polynomial,

[Numpy-discussion] poly1d left versus right multiplication with np numbers

I just had a hard to find bug in my program. poly1d treats numpy scalars differently than python numbers when left or right multiplication is used. Essentially, if the first term is the numpy scalar, multiplied by a polynomial, then the result is an np.array. If the order is reversed, then the re

Re: [Numpy-discussion] Numpy 1.3 release date ?

> 2009/2/4 David Cournapeau : > Scott Sinclair wrote: >> >> There are a bunch of documentation patches that should to be reviewed >> and applied to SVN before the release (especially those marked 'Needs >> review' or better). >> >> http://docs.scipy.org/numpy/patch/ > > In my mind, documentations f

Re: [Numpy-discussion] Numpy 1.3 release date ?

Scott Sinclair wrote: > > There are a bunch of documentation patches that should to be reviewed > and applied to SVN before the release (especially those marked 'Needs > review' or better). > > http://docs.scipy.org/numpy/patch/ In my mind, documentations fixes are much less important than code, n

Re: [Numpy-discussion] Error building numpy documentation

> 2009/2/4 Nadav Horesh : > I just dowloads the latest numpy's svn version and tried to build its > documentation with > > $ make latex > > on the doc subdirectory, and got the following error message: > > writing... Sphinx error: > too many nesting section levels for LaTeX, at heading: > numpy.ma.

[Numpy-discussion] Resolver One -- .NET spreadsheet with NumPy -- beta testers?

Hi all We're about to release the first public beta of Resolver One, our Pythonic spreadsheet, with (rather basic) NumPy integration. It requires 32-bit Windows and .NET 2.0SP1 to run, so it may not be appropriate for everyone, but -- if anyone is interested in playing with it -- it would be r

Re: [Numpy-discussion] Few minor issues with numscons

Brian Granger wrote: >> The releases are on Pypi for quite some time. I converted the repo to >> git and put it on github, but I have not really worked on numscons for >> several months now for lack of time ( and because numscons it mostly >> "done" and the main limitations of numscons are not fixa

Re: [Numpy-discussion] Numpy 1.3 release date ?

Wed, 04 Feb 2009 11:04:25 +0900, David Cournapeau wrote: [clip] > Talking about the things I have worked on for 1.3, I did not have the > time to finish everything. The things which I would like to be done > before a 1.3.0 release are: > - fix formatting issues that Pauli and me worked on (for loc

[Numpy-discussion] Error building numpy documentation

I just dowloads the latest numpy's svn version and tried to build its documentation with $ make latex on the doc subdirectory, and got the following error message: writing... Sphinx error: too many nesting section levels for LaTeX, at heading: numpy.ma.MaskedArray.__lt__ make: *** [latex] Error