Re: [Numpy-discussion] Cutting 1.0.2 release

2007-02-01 Thread Sven Schreiber
Travis Oliphant schrieb: > I think it's time for the 1.0.2 release of NumPy. > > What outstanding issues need to be resolved before we do it? > Hi, I just used real_if_close for the first time, and promptly discovered that it turns matrix input into array output: >>> import numpy as n >>> n._

Re: [Numpy-discussion] Cutting 1.0.2 release

2007-01-31 Thread Gary Ruben
Thanks Fernando, Good idea. I'll apply your suggestion. Gary Fernando Perez wrote: > On 1/31/07, Gary Ruben <[EMAIL PROTECTED]> wrote: >> Actually, I just realised; it's not an ipython problem. I think it's a >> matplotlib problem. I'll report it there. > > Until mpl drops support for the compat

Re: [Numpy-discussion] Cutting 1.0.2 release

2007-01-31 Thread Fernando Perez
On 1/31/07, Gary Ruben <[EMAIL PROTECTED]> wrote: > Actually, I just realised; it's not an ipython problem. I think it's a > matplotlib problem. I'll report it there. Until mpl drops support for the compatibility layers, you may want to set up a simple pylab profile. In ~/.ipython make a file cal

Re: [Numpy-discussion] Cutting 1.0.2 release

2007-01-31 Thread Gary Ruben
Actually, I just realised; it's not an ipython problem. I think it's a matplotlib problem. I'll report it there. Gary R. Steve Lianoglou wrote: >> Thanks Alan & Chris, >> >> My apologies. I was trying ones(), zeros() and empty() in ipython >> 0.7.2 >> with the -pylab option and getting the wro

Re: [Numpy-discussion] Cutting 1.0.2 release

2007-01-31 Thread Steve Lianoglou
> Thanks Alan & Chris, > > My apologies. I was trying ones(), zeros() and empty() in ipython > 0.7.2 > with the -pylab option and getting the wrong functions. On my system, > ipython -pylab imports the namespace of the oldnumeric wrapper > versions > of ones(), zeros() and empty() and I had ass

Re: [Numpy-discussion] Cutting 1.0.2 release

2007-01-31 Thread Gary Ruben
Thanks Alan & Chris, My apologies. I was trying ones(), zeros() and empty() in ipython 0.7.2 with the -pylab option and getting the wrong functions. On my system, ipython -pylab imports the namespace of the oldnumeric wrapper versions of ones(), zeros() and empty() and I had assumed these were

Re: [Numpy-discussion] Cutting 1.0.2 release

2007-01-30 Thread Christopher Barker
Gary Ruben wrote: > One question, which may be an issue: Should ones, zeros and empty be > generating arrays of floats by default now? >>> import numpy as N >>> N.ones((3,)).dtype dtype('float64') >>> N.zeros((3,)).dtype dtype('float64') >>> N.__version__ '1.0.1' -Chris -- Christopher

Re: [Numpy-discussion] Cutting 1.0.2 release

2007-01-30 Thread Alan G Isaac
On Tue, 30 Jan 2007, Gary Ruben apparently wrote: > One question, which may be an issue: Should ones, zeros > and empty be generating arrays of floats by default now? >>> import numpy as n >>> z = n.zeros((2,2)) >>> z.dtype dtype('float64') >>> o = n.ones((2,2)) >>> o.dtype dtype('float64') >>>

Re: [Numpy-discussion] Cutting 1.0.2 release

2007-01-30 Thread Gary Ruben
One question, which may be an issue: Should ones, zeros and empty be generating arrays of floats by default now? Gary R. Travis Oliphant wrote: > I think it's time for the 1.0.2 release of NumPy. > > What outstanding issues need to be resolved before we do it? > > Hopefully, we can do it by

[Numpy-discussion] Cutting 1.0.2 release

2007-01-29 Thread Travis Oliphant
I think it's time for the 1.0.2 release of NumPy. What outstanding issues need to be resolved before we do it? Hopefully, we can do it by the end of the week. -Travis ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scip