Hi,
On Sat, Mar 30, 2013 at 7:02 PM, josef.p...@gmail.com wrote:
On Sat, Mar 30, 2013 at 8:29 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Sat, Mar 30, 2013 at 7:50 PM, josef.p...@gmail.com wrote:
On Sat, Mar 30, 2013 at 7:31 PM, Bradley M. Froehle
brad.froe...@gmail.com
Hi,
On Sat, Mar 30, 2013 at 7:02 PM, josef.p...@gmail.com wrote:
On Sat, Mar 30, 2013 at 8:29 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Sat, Mar 30, 2013 at 7:50 PM, josef.p...@gmail.com wrote:
On Sat, Mar 30, 2013 at 7:31 PM, Bradley M. Froehle
brad.froe...@gmail.com
Hi,
We were teaching today, and found ourselves getting very confused
about ravel and shape in numpy.
Summary
--
There are two separate ideas needed to understand ordering in ravel and reshape:
Idea 1): ravel / reshape can proceed from the last axis to the first,
or the first to
Hi Ondrej,
On Thu, Feb 7, 2013 at 3:18 PM, Ondřej Čertík ondrej.cer...@gmail.com wrote:
On Thu, Feb 7, 2013 at 12:29 PM, Chris Barker - NOAA Federal
chris.bar...@noaa.gov wrote:
On Thu, Feb 7, 2013 at 11:38 AM, Matthew Brett matthew.br...@gmail.com
wrote:
a) If we cannot build Scipy now
Hi,
On Tue, Feb 26, 2013 at 12:20 AM, Pierre Haessig
pierre.haes...@crans.org wrote:
Hi,
Le 22/02/2013 17:40, Matthew Brett a écrit :
From complete ignorance, do you think it is an option to allow a
(n_left, n_right) tuple as a value for 'mode'?
That may be an option. Another one would
Hi,
On Thu, Feb 21, 2013 at 10:00 AM, Pierre Haessig
pierre.haes...@crans.org wrote:
Hi everybody,
(just coming from a discussion on the performance of Matplotlib's
(x)corr function which uses np.correlate)
There have been already many discussions on how to compute
(cross-)correlations of
Hi,
On Wed, Feb 6, 2013 at 10:59 PM, Ondřej Čertík ondrej.cer...@gmail.com wrote:
On Wed, Feb 6, 2013 at 10:41 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Wed, Feb 6, 2013 at 10:21 PM, Ondřej Čertík ondrej.cer...@gmail.com
wrote:
On Wed, Feb 6, 2013 at 9:20 PM, Dag Sverre
Hi,
On Thu, Feb 7, 2013 at 10:47 AM, Ralf Gommers ralf.gomm...@gmail.com wrote:
On Thu, Feb 7, 2013 at 7:41 AM, Matthew Brett matthew.br...@gmail.com
wrote:
I think you will need a developer's license for MKL for Numpy. Ralf -
any ETA for those?
No, I'll have to ask again.
I think
Hi,
On Thu, Feb 7, 2013 at 10:47 AM, Ralf Gommers ralf.gomm...@gmail.com wrote:
On Thu, Feb 7, 2013 at 7:41 AM, Matthew Brett matthew.br...@gmail.com
wrote:
I think you will need a developer's license for MKL for Numpy. Ralf -
any ETA for those?
No, I'll have to ask again.
I think
Hi,
On Thu, Feb 7, 2013 at 11:05 AM, Ralf Gommers ralf.gomm...@gmail.com wrote:
On Thu, Feb 7, 2013 at 7:59 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Can we defer the Scipy build until after the Numpy build?
That doesn't sound like a good idea to me.
I must say I'm
Hi,
On Thu, Feb 7, 2013 at 12:29 PM, Chris Barker - NOAA Federal
chris.bar...@noaa.gov wrote:
On Thu, Feb 7, 2013 at 11:38 AM, Matthew Brett matthew.br...@gmail.com
wrote:
a) If we cannot build Scipy now, it may or may not be acceptable to
release numpy now. I think it is, you (Ralf) think
Hi,
On Wed, Feb 6, 2013 at 10:48 AM, Ralf Gommers ralf.gomm...@gmail.com wrote:
On Wed, Feb 6, 2013 at 1:32 AM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Tue, Feb 5, 2013 at 3:04 PM, Christoph Gohlke cgoh...@uci.edu wrote:
On 2/5/2013 10:51 AM, Matthew Brett wrote:
Hi
Hi,
On Wed, Feb 6, 2013 at 1:36 PM, Ralf Gommers ralf.gomm...@gmail.com wrote:
On Wed, Feb 6, 2013 at 8:46 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Wed, Feb 6, 2013 at 10:48 AM, Ralf Gommers ralf.gomm...@gmail.com
wrote:
On Wed, Feb 6, 2013 at 1:32 AM, Matthew
Hi,
On Wed, Feb 6, 2013 at 9:20 PM, Dag Sverre Seljebotn
d.s.seljeb...@astro.uio.no wrote:
On 02/07/2013 12:16 AM, Matthew Brett wrote:
Hi,
On Wed, Feb 6, 2013 at 1:36 PM, Ralf Gommers ralf.gomm...@gmail.com wrote:
On Wed, Feb 6, 2013 at 8:46 PM, Matthew Brett matthew.br...@gmail.com
Hi,
On Wed, Feb 6, 2013 at 10:21 PM, Ondřej Čertík ondrej.cer...@gmail.com wrote:
On Wed, Feb 6, 2013 at 9:20 PM, Dag Sverre Seljebotn
d.s.seljeb...@astro.uio.no wrote:
On 02/07/2013 12:16 AM, Matthew Brett wrote:
[...]
Can you clarify the people you think will get stuck? I think I'm
right
Hi,
On Tue, Feb 5, 2013 at 6:03 AM, Jonathan T. Niehof jnie...@lanl.gov wrote:
On 02/04/2013 06:09 PM, Matthew Brett wrote:
The problem with not providing these binaries is that they are at the
bottom of everyone's stack, so a delay in numpy holds everyone back.
OTOH, so far it's been
Hi,
On Mon, Feb 4, 2013 at 5:09 PM, Matthew Brett matthew.br...@gmail.com wrote:
Hi,
On Mon, Feb 4, 2013 at 3:46 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Mon, Feb 4, 2013 at 4:04 PM, Robert Kern robert.k...@gmail.com wrote:
On Mon, Feb 4, 2013 at 10:38 PM, Matthew Brett
Hi,
On Tue, Feb 5, 2013 at 3:04 PM, Christoph Gohlke cgoh...@uci.edu wrote:
On 2/5/2013 10:51 AM, Matthew Brett wrote:
Hi,
On Mon, Feb 4, 2013 at 5:09 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Mon, Feb 4, 2013 at 3:46 PM, Charles R Harris
charlesr.har...@gmail.com wrote
Hi,
On Tue, Feb 5, 2013 at 4:55 PM, Chris Barker - NOAA Federal
chris.bar...@noaa.gov wrote:
On Tue, Feb 5, 2013 at 4:32 PM, Matthew Brett matthew.br...@gmail.com wrote:
4) Numpy-MKL requires the Intel runtime DLLs (MKL is linked statically
btw). I ship those with the installers and append
Hi,
On Mon, Feb 4, 2013 at 12:27 PM, Ondřej Čertík ondrej.cer...@gmail.com wrote:
On Sun, Feb 3, 2013 at 2:57 AM, David Cournapeau courn...@gmail.com wrote:
On Sun, Feb 3, 2013 at 12:28 AM, josef.p...@gmail.com wrote:
On Sat, Feb 2, 2013 at 6:14 PM, Matthew Brett matthew.br...@gmail.com
Hi,
On Mon, Feb 4, 2013 at 12:55 PM, Ralf Gommers ralf.gomm...@gmail.com wrote:
On Mon, Feb 4, 2013 at 9:39 PM, Nathaniel Smith n...@pobox.com wrote:
On Mon, Feb 4, 2013 at 12:36 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Mon, Feb 4, 2013 at 12:27 PM, Ondřej Čertík
Hi,
On Mon, Feb 4, 2013 at 1:15 PM, Ralf Gommers ralf.gomm...@gmail.com wrote:
On Mon, Feb 4, 2013 at 10:06 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Mon, Feb 4, 2013 at 12:55 PM, Ralf Gommers ralf.gomm...@gmail.com
wrote:
On Mon, Feb 4, 2013 at 9:39 PM, Nathaniel
Hi,
On Mon, Feb 4, 2013 at 3:46 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Mon, Feb 4, 2013 at 4:04 PM, Robert Kern robert.k...@gmail.com wrote:
On Mon, Feb 4, 2013 at 10:38 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Mon, Feb 4, 2013 at 1:15 PM, Ralf Gommers
Hi,
On Mon, Feb 4, 2013 at 5:09 PM, Matthew Brett matthew.br...@gmail.com wrote:
Hi,
On Mon, Feb 4, 2013 at 3:46 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Mon, Feb 4, 2013 at 4:04 PM, Robert Kern robert.k...@gmail.com wrote:
On Mon, Feb 4, 2013 at 10:38 PM, Matthew Brett
Hi,
I see there is no Windows 64 bit installer for the 1.7 rc1.
Is there any prospect of a 64 bit installer for the full release?
Can I help? I have a Windows 7 64 bit machine that I use as a build
slave; I am happy to give access.
Cheers,
Matthew
Hi,
On Sun, Jan 20, 2013 at 6:10 PM, Olivier Delalleau sh...@keba.be wrote:
2013/1/18 Matthew Brett matthew.br...@gmail.com:
Hi,
On Fri, Jan 18, 2013 at 7:58 PM, Chris Barker - NOAA Federal
chris.bar...@noaa.gov wrote:
On Fri, Jan 18, 2013 at 4:39 AM, Olivier Delalleau sh...@keba.be wrote
Hi,
On Fri, Jan 18, 2013 at 1:48 PM, Pierre Haessig
pierre.haes...@crans.org wrote:
Hi,
Le 17/01/2013 23:31, Matthew Brett a écrit :
Would it be too weird or clumsy to extend the empty and empty_like functions
to do the filling?
np.empty((10, 10), fill=np.nan)
np.empty_like(my_arr, fill
Hi,
On Fri, Jan 18, 2013 at 7:58 PM, Chris Barker - NOAA Federal
chris.bar...@noaa.gov wrote:
On Fri, Jan 18, 2013 at 4:39 AM, Olivier Delalleau sh...@keba.be wrote:
Le vendredi 18 janvier 2013, Chris Barker - NOAA Federal a écrit :
If you check again the examples in this thread exhibiting
Hi,
On Wed, Jan 9, 2013 at 6:07 PM, Dag Sverre Seljebotn
d.s.seljeb...@astro.uio.no wrote:
On 01/09/2013 06:22 PM, Chris Barker - NOAA Federal wrote:
On Wed, Jan 9, 2013 at 7:09 AM, Nathaniel Smith n...@pobox.com wrote:
This is a general issue applying to data which is read from real-world
Hi,
On Thu, Jan 17, 2013 at 10:10 PM, Benjamin Root ben.r...@ou.edu wrote:
On Thu, Jan 17, 2013 at 5:04 PM, Eric Firing efir...@hawaii.edu wrote:
On 2013/01/17 4:13 AM, Pierre Haessig wrote:
Hi,
Le 14/01/2013 20:05, Benjamin Root a écrit :
I do like the way you are thinking in terms
Hi,
On Thu, Jan 17, 2013 at 10:27 PM, Mark Wiebe mwwi...@gmail.com wrote:
On Thu, Jan 17, 2013 at 2:10 PM, Benjamin Root ben.r...@ou.edu wrote:
On Thu, Jan 17, 2013 at 5:04 PM, Eric Firing efir...@hawaii.edu wrote:
On 2013/01/17 4:13 AM, Pierre Haessig wrote:
Hi,
Le 14/01/2013
Hi,
On Fri, Jan 18, 2013 at 1:04 AM, Chris Barker - NOAA Federal
chris.bar...@noaa.gov wrote:
On Thu, Jan 17, 2013 at 6:26 AM, Matthew Brett matthew.br...@gmail.com
wrote:
I am starting to wonder if we should aim for making
* scalar and array casting rules the same;
* Python int / float
Hi,
On Mon, Jan 14, 2013 at 12:19 AM, David Cournapeau courn...@gmail.com wrote:
On Sun, Jan 13, 2013 at 5:26 PM, Nathaniel Smith n...@pobox.com wrote:
On Sun, Jan 13, 2013 at 7:03 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
Now that 1.7 is nearing release, it's time to look forward
Hi,
On Mon, Jan 14, 2013 at 10:35 AM, Jaakko Luttinen
jaakko.lutti...@aalto.fi wrote:
On 01/14/2013 12:53 AM, Matthew Brett wrote:
On Sun, Jan 13, 2013 at 10:46 PM, Jaakko Luttinen
jaakko.lutti...@aalto.fi wrote:
I'm a bit stuck trying to make numpydoc Python 3 compatible. I made
setup.py
Hi,
On Mon, Jan 14, 2013 at 9:02 AM, Dave Hirschfeld
dave.hirschf...@gmail.com wrote:
Robert Kern robert.kern at gmail.com writes:
One alternative that does not expand the API with two-liners is to let
the ndarray.fill() method return self:
a = np.empty(...).fill(20.0)
Hi,
On Sun, Jan 13, 2013 at 5:27 PM, Nathaniel Smith n...@pobox.com wrote:
Hi all,
PR 2875 adds two new functions, that generalize zeros(), ones(),
zeros_like(), ones_like(), by simply taking an arbitrary fill value:
https://github.com/numpy/numpy/pull/2875
So
np.ones((10, 10))
is the
On Sun, Jan 13, 2013 at 11:24 PM, Robert Kern robert.k...@gmail.com wrote:
On Sun, Jan 13, 2013 at 6:27 PM, Nathaniel Smith n...@pobox.com wrote:
Hi all,
PR 2875 adds two new functions, that generalize zeros(), ones(),
zeros_like(), ones_like(), by simply taking an arbitrary fill value:
Hi,
On Mon, Jan 7, 2013 at 10:58 PM, Andrew Collette
andrew.colle...@gmail.com wrote:
Hi,
Taking 2) first, in this example:
return self.f[dataset_name][...] + heightmap
assuming it is not going to upcast, would you rather it overflow than
raise an error? Why? The second seems more
Hi,
On Fri, Jan 4, 2013 at 5:25 PM, Andrew Collette
andrew.colle...@gmail.com wrote:
I agree the current behavior is confusing. Regardless of the details
of what to do, I suppose my main objection is that, to me, it's really
unexpected that adding a number to an array could result in an
and doesn't support Python 3.x. Most
recent version is at: https://github.com/matthew-brett/bdist_mpkg, for
previous versions numpy releases I've used that at commit e81a58a471
There has been recent discussion on the pythonmac list about this --
some waffling about how important it is -- though I
Hi,
On Mon, Jan 7, 2013 at 5:48 PM, Chris Barker - NOAA Federal
chris.bar...@noaa.gov wrote:
On Mon, Jan 7, 2013 at 5:31 AM, Matthew Brett matthew.br...@gmail.com wrote:
I updated my fork of bdist_mpkg with Python 3k support. It doesn't
have any tests that I could see, but I've run
Hi,
On Mon, Jan 7, 2013 at 4:33 PM, Andrew Collette
andrew.colle...@gmail.com wrote:
Hi Matthew,
I realized when I thought about it, that I did not have a clear idea
of your exact use case. How does the user specify the thing to add,
and why do you need to avoid an error in the case that
Hi,
On Mon, Jan 7, 2013 at 8:50 PM, Andrew Collette
andrew.colle...@gmail.com wrote:
Hi Matthew,
Just to be clear, you mean you might have something like this?
def my_func('array_name', some_offset):
arr = load_somehow('array_name') # dtype hitherto unknown
return arr + some_offset
Hi,
On Mon, Jan 7, 2013 at 9:18 PM, Andrew Collette
andrew.colle...@gmail.com wrote:
Hi Matthew,
In this case I think you'd probably agree it would be reasonable to
raise an error - all other things being equal?
No, I don't agree. I want there to be some default semantics I can
rely on.
Hi,
On Mon, Jan 7, 2013 at 10:03 PM, Andrew Collette
andrew.colle...@gmail.com wrote:
Hi Matthew,
Ah - well - I only meant that raising an error in the example would be
no more surprising than raising an error at the python prompt. Do you
agree with that? I mean, if the user knew that:
Hi,
On Sun, Jan 6, 2013 at 5:53 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Sat, Jan 5, 2013 at 2:31 PM, Nathaniel Smith n...@pobox.com wrote:
On 5 Jan 2013 12:16, Matthew Brett matthew.br...@gmail.com wrote:
Hi,
Following on from Nathaniel's explorations of the scalar
Hi,
Following on from Nathaniel's explorations of the scalar - array
casting rules, some resources on rank-0 arrays.
The discussion that Nathaniel tracked down on rank-0 arrays; it also
makes reference to casting. The rank-0 arrays seem to have been one
way of solving the problem of maintaining
Hi,
On Sat, Jan 5, 2013 at 12:15 PM, Matthew Brett matthew.br...@gmail.com wrote:
Hi,
Following on from Nathaniel's explorations of the scalar - array
casting rules, some resources on rank-0 arrays.
The discussion that Nathaniel tracked down on rank-0 arrays; it also
makes reference
Hi,
On Fri, Jan 4, 2013 at 4:54 PM, Matthew Brett matthew.br...@gmail.com wrote:
Hi,
On Fri, Jan 4, 2013 at 4:01 PM, Andrew Collette
andrew.colle...@gmail.com wrote:
From a more basic perspective, I think that adding a number to an
array should never raise an exception. I've not used any
Hi,
On Sat, Jan 5, 2013 at 2:38 PM, Nathaniel Smith n...@pobox.com wrote:
On Sat, Jan 5, 2013 at 12:32 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Fri, Jan 4, 2013 at 4:54 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Fri, Jan 4, 2013 at 4:01 PM, Andrew Collette
Hi,
On Sat, Jan 5, 2013 at 4:16 PM, Nathaniel Smith n...@pobox.com wrote:
On 5 Jan 2013 15:59, Matthew Brett matthew.br...@gmail.com wrote:
Hi,
On Sat, Jan 5, 2013 at 2:38 PM, Nathaniel Smith n...@pobox.com wrote:
On Sat, Jan 5, 2013 at 12:32 PM, Matthew Brett matthew.br...@gmail.com
Hi,
Reading the discussion on the scalar casting rule change I realized I
was hazy on the use-cases that led to the rule that scalars cast
differently from arrays.
My impression was that the primary use-case was for lower-precision
floats. That is, when you have a large float32 arr, you do not
Hi,
On Fri, Jan 4, 2013 at 4:01 PM, Andrew Collette
andrew.colle...@gmail.com wrote:
From a more basic perspective, I think that adding a number to an
array should never raise an exception. I've not used any other
language in which this behavior takes place. In C, you have rollover
Hi,
On Sun, Dec 23, 2012 at 8:53 PM, Ralf Gommers ralf.gomm...@gmail.com wrote:
On Sun, Dec 23, 2012 at 7:54 PM, Ondřej Čertík ondrej.cer...@gmail.com
wrote:
Hi Matthew,
On Sat, Dec 22, 2012 at 9:40 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
I noticed that enabling
Hi,
On Sun, Dec 23, 2012 at 7:00 PM, Nathaniel Smith n...@pobox.com wrote:
On Sat, Dec 22, 2012 at 5:36 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Thu, Dec 20, 2012 at 5:39 PM, Nathaniel Smith n...@pobox.com wrote:
On Thu, Dec 20, 2012 at 11:46 PM, Matthew Brett matthew.br
Hi,
On Sun, Dec 23, 2012 at 6:54 PM, Ondřej Čertík ondrej.cer...@gmail.com wrote:
Hi Matthew,
On Sat, Dec 22, 2012 at 9:40 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
I noticed that enabling the doctests on the 1.7.x maintenance branch
caused lots and lots of doctest failures
Hi,
On Sun, Dec 23, 2012 at 8:56 AM, Dag Sverre Seljebotn
d.s.seljeb...@astro.uio.no wrote:
On 12/22/2012 06:36 PM, Matthew Brett wrote:
Hi,
On Thu, Dec 20, 2012 at 5:39 PM, Nathaniel Smith n...@pobox.com wrote:
On Thu, Dec 20, 2012 at 11:46 PM, Matthew Brett matthew.br...@gmail.com
wrote
Hi,
On Thu, Dec 20, 2012 at 5:39 PM, Nathaniel Smith n...@pobox.com wrote:
On Thu, Dec 20, 2012 at 11:46 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Travis - I think you are suggesting that there should be no one
person in charge of numpy, and I think this is very unlikely to work
Hi,
On Fri, Dec 21, 2012 at 12:14 AM, Travis Oliphant tra...@continuum.io wrote:
On Dec 20, 2012, at 7:39 PM, Nathaniel Smith wrote:
On Thu, Dec 20, 2012 at 11:46 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Travis - I think you are suggesting that there should be no one
person
Hi,
I noticed that enabling the doctests on the 1.7.x maintenance branch
caused lots and lots of doctest failures.
(np-devel)[mb312@blair ~/dev_trees]$ python -c 'import numpy as np;
np.test(doctests=True)'
1.7.0rc1.dev-1e8fcdf
Running unit tests and doctests for numpy
NumPy version
Hi,
[Travis wrote...]
My strong suggestion is that development discussions of the project continue
on
this list with consensus among the active participants being the goal for
development. I don't think 100% consensus is a rigid requirement --- but
certainly a super-majority should be the
Hi,
I wanted to check that everyone knows about and is happy with the
scalar casting changes from 1.6.0.
Specifically, the rules for (array, scalar) casting have changed such
that the resulting dtype depends on the _value_ of the scalar.
Mark W has documented these changes here:
Hi,
On Mon, Nov 12, 2012 at 1:11 PM, Nathaniel Smith n...@pobox.com wrote:
On Mon, Nov 12, 2012 at 8:54 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
I wanted to check that everyone knows about and is happy with the
scalar casting changes from 1.6.0.
Specifically, the rules
Hi,
On Mon, Nov 12, 2012 at 8:15 PM, Benjamin Root ben.r...@ou.edu wrote:
On Monday, November 12, 2012, Olivier Delalleau wrote:
2012/11/12 Nathaniel Smith n...@pobox.com
On Mon, Nov 12, 2012 at 8:54 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
I wanted to check
Hi,
On Thu, Oct 4, 2012 at 10:29 AM, Matthew Brett matthew.br...@gmail.com wrote:
Hi,
On Thu, Oct 4, 2012 at 7:35 AM, Ralf Gommers ralf.gomm...@gmail.com wrote:
On Thu, Oct 4, 2012 at 12:14 AM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Wed, Oct 3, 2012 at 10:51 PM, Ralf
Hi,
On Thu, Oct 4, 2012 at 7:35 AM, Ralf Gommers ralf.gomm...@gmail.com wrote:
On Thu, Oct 4, 2012 at 12:14 AM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Wed, Oct 3, 2012 at 10:51 PM, Ralf Gommers ralf.gomm...@gmail.com
wrote:
On Wed, Oct 3, 2012 at 11:29 PM, Matthew
Hi,
On Fri, Sep 21, 2012 at 1:05 AM, Frédéric Bastien no...@nouiz.org wrote:
Hi,
Finally, the change about the casting rule was done in NumPy 1.6. It
is our test that checked specifically for numpy 1.6 behavior. But
adding the test to make sure it don't change is an excellent idea.
Sorry -
Hi,
On Wed, Oct 3, 2012 at 10:17 PM, Ralf Gommers ralf.gomm...@gmail.com wrote:
On Mon, Oct 1, 2012 at 10:47 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Mon, Oct 1, 2012 at 9:42 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
One of our kind users pointed out
Hi,
On Wed, Oct 3, 2012 at 10:51 PM, Ralf Gommers ralf.gomm...@gmail.com wrote:
On Wed, Oct 3, 2012 at 11:29 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Wed, Oct 3, 2012 at 10:17 PM, Ralf Gommers ralf.gomm...@gmail.com
wrote:
On Mon, Oct 1, 2012 at 10:47 PM, Matthew
Hi,
On Mon, Oct 1, 2012 at 9:04 AM, Pierre Haessig pierre.haes...@crans.org wrote:
Hi,
Le 28/09/2012 21:02, Neal Becker a écrit :
In [19]: u = np.arange (10)
In [20]: v = np.arange (10)
In [21]: u[v] = u
In [22]: u[v] = np.arange(11)
silence...
I've same behavior with my numpy 1.6.2.
Hi,
One of our kind users pointed out an error when using easy_install to
install our package nipy. I've reproduced it now on a bare package
using numpy distutils and having a trivial extension:
https://github.com/matthew-brett/apkg
To reproduce:
git clone git://github.com/mathew-brett
Hi,
On Mon, Oct 1, 2012 at 9:42 PM, Matthew Brett matthew.br...@gmail.com wrote:
Hi,
One of our kind users pointed out an error when using easy_install to
install our package nipy. I've reproduced it now on a bare package
using numpy distutils and having a trivial extension:
https
Hi,
On Fri, Sep 28, 2012 at 3:45 PM, Nathaniel Smith n...@pobox.com wrote:
Hi all,
I've gotten a pull request for scikits-sparse to switch it to using
numpy.distutils:
https://github.com/njsmith/scikits-sparse/pull/2
Overall this seems fair enough, finding libraries is a pain and
Hi,
On Sun, Sep 9, 2012 at 6:12 PM, Frédéric Bastien no...@nouiz.org wrote:
The third is releated to change to the casting rules in numpy. Before
a scalar complex128 * vector float32 gived a vector of dtype
complex128. Now it give a vector of complex64. The reason is that now
the scalar of
Hi,
On Fri, Sep 14, 2012 at 11:25 PM, Han Genuit hangen...@gmail.com wrote:
I think there is something wrong with the implementation.. I would
expect each incoming array in PyArray_ConcatenateFlattenedArrays to be
flattened and the sizes of all of them added into a one-dimensional
shape. Now
Hi,
I just noticed that Python 3 raises an error for 0 dimensional numpy
arrays. Here's Python 2.6:
In [14]: a = np.array(1.1)
In [15]: round(a)
Out[15]: 1.0
and Python 3.2:
In [3]: a = np.array(1.1)
In [4]: round(a)
Hi,
On Thu, Sep 13, 2012 at 7:00 PM, Matthew Brett matthew.br...@gmail.com wrote:
Hi,
On Thu, Sep 13, 2012 at 11:31 AM, Matthew Brett matthew.br...@gmail.com
wrote:
On Wed, Sep 12, 2012 at 4:19 PM, Nathaniel Smith n...@pobox.com wrote:
On Wed, Sep 12, 2012 at 2:46 PM, Matthew Brett
Hi,
While writing some tests for np.concatenate, I ran foul of this code:
if (axis = NPY_MAXDIMS) {
ret = PyArray_ConcatenateFlattenedArrays(narrays, arrays, NPY_CORDER);
}
else {
ret = PyArray_ConcatenateArrays(narrays, arrays, axis);
}
in multiarraymodule.c
On Wed, Sep 12, 2012 at 4:19 PM, Nathaniel Smith n...@pobox.com wrote:
On Wed, Sep 12, 2012 at 2:46 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
I just noticed that this works for numpy 1.6.1:
In [36]: np.concatenate(([2, 3], [1]), 1)
Out[36]: array([2, 3, 1])
but the beta
Hi,
On Wed, Sep 12, 2012 at 10:24 PM, Ondřej Čertík ondrej.cer...@gmail.com wrote:
Hi Matt,
On Wed, Sep 12, 2012 at 1:27 PM, Travis Oliphant tra...@continuum.io wrote:
Is this intended? Is there a performance reason to keep the same
strides in 1.7.0?
I believe that this could be because
Hi,
On Thu, Sep 13, 2012 at 3:01 PM, Travis Oliphant tra...@continuum.io wrote:
On Sep 13, 2012, at 8:40 AM, Nathaniel Smith wrote:
On Thu, Sep 13, 2012 at 11:12 AM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
While writing some tests for np.concatenate, I ran foul of this code
Hi,
On Thu, Sep 13, 2012 at 11:31 AM, Matthew Brett matthew.br...@gmail.com wrote:
On Wed, Sep 12, 2012 at 4:19 PM, Nathaniel Smith n...@pobox.com wrote:
On Wed, Sep 12, 2012 at 2:46 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
I just noticed that this works for numpy 1.6.1
Hi,
I just noticed that this works for numpy 1.6.1:
In [36]: np.concatenate(([2, 3], [1]), 1)
Out[36]: array([2, 3, 1])
but the beta release branch:
In [3]: np.concatenate(([2, 3], [1]), 1)
---
IndexError
Hi,
We hit a subtle behavior change for the ``astype`` array method
between 1.6.1 and 1.7.0 beta.
In 1.6.1:
In [18]: a = np.arange(24).reshape((2, 3, 4)).transpose((1, 2, 0))
In [19]: a.flags
Out[19]:
C_CONTIGUOUS : False
F_CONTIGUOUS : False
OWNDATA : False
WRITEABLE : True
ALIGNED
Hi,
On Wed, Sep 12, 2012 at 7:58 PM, Travis Oliphant tra...@continuum.io wrote:
On Sep 12, 2012, at 1:36 PM, Matthew Brett wrote:
Hi,
We hit a subtle behavior change for the ``astype`` array method
between 1.6.1 and 1.7.0 beta.
In 1.6.1:
In [18]: a = np.arange(24).reshape((2, 3, 4
Hi,
On Wed, Sep 5, 2012 at 7:05 PM, David Cournapeau courn...@gmail.com wrote:
Hi Frederic,
On Wed, Sep 5, 2012 at 6:36 PM, Frédéric Bastien no...@nouiz.org wrote:
Hi,
I spent up to now 2 or 3 days making change to Theano to support numpy
1.7b1. But now, I just find an interface change
Hi,
On Tue, Sep 4, 2012 at 11:15 AM, Nathaniel Smith n...@pobox.com wrote:
The last two Travis builds of master have failed consistently with the
same error:
http://travis-ci.org/#!/numpy/numpy/builds
It looks like a real failure -- we're getting the same error on every
build variant, some
Hi,
On Tue, Sep 4, 2012 at 2:18 PM, Nathaniel Smith n...@pobox.com wrote:
On Tue, Sep 4, 2012 at 1:47 PM, Scott Sinclair
scott.sinclair...@gmail.com wrote:
On 4 September 2012 12:23, Matthew Brett matthew.br...@gmail.com wrote:
On Tue, Sep 4, 2012 at 11:15 AM, Nathaniel Smith n...@pobox.com
Hi,
On Fri, Aug 17, 2012 at 2:25 PM, Sayth Renshaw flebber.c...@gmail.com wrote:
Hi Sayth,
On Thu, Aug 16, 2012 at 8:51 PM, Sayth Renshaw flebber.c...@gmail.com
wrote:
Hi
I was just wondering if the current absence of 64bit builds was as a result
of an infrastructure or funding concern.
Hi,
On Sat, Jul 14, 2012 at 3:45 PM, Travis Oliphant tra...@continuum.io wrote:
Hey all,
We are nearing a code-freeze for NumPy 1.7. Are there any last-minute
changes people are wanting to push into NumPy 1.7? We should discuss them as
soon as possible.
I'm proposing a code-freeze at
Hi,
On Tue, Jun 26, 2012 at 7:29 PM, Matthew Brett matthew.br...@gmail.com wrote:
Hi,
On Tue, Jun 26, 2012 at 5:04 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Tue, Jun 26, 2012 at 5:46 PM, Matthew Brett matthew.br...@gmail.com
wrote:
Hi,
On Tue, Jun 26, 2012 at 4:39 PM
On Fri, Jul 13, 2012 at 9:24 AM, Robert Kern robert.k...@gmail.com wrote:
On Thu, Jul 12, 2012 at 10:32 PM, Chao YUE chaoyue...@gmail.com wrote:
Thanks all for the discussion. Actually I am trying to use something like
numpy ndarray indexing in the function. Like when I call:
Hi,
On Sun, Jul 8, 2012 at 2:36 AM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
On Fri, Jul 6, 2012 at 1:30 PM, McCully, Dwayne (NIH/NLM/LHC) [C]
dmccu...@mail.nih.gov wrote:
Hope this is the right list to post this problem! I’m getting two errors
when running a numpy (see below).
Hi,
On Sat, Jun 30, 2012 at 1:35 AM, Dag Sverre Seljebotn
d.s.seljeb...@astro.uio.no wrote:
+1 on scicomp.stackexchange.com
For it to work, one would need to actively push users towards it though...so
it would require a very clear pronouncement.
Matthew: I'm happy with the split we did with
Hi,
On Sat, Jun 30, 2012 at 12:29 PM, John Hunter jdh2...@gmail.com wrote:
On Fri, Jun 29, 2012 at 2:20 PM, Jim Vickroy jim.vick...@noaa.gov wrote:
As a lurker and user, I too wish for a distinct numpy-users list. -- jv
This thread is a perfect example of why another list is needed.
Hi,
On Sat, Jun 30, 2012 at 1:05 PM, Dag Sverre Seljebotn
d.s.seljeb...@astro.uio.no wrote:
On 06/30/2012 09:37 PM, Matthew Brett wrote:
Hi,
On Sat, Jun 30, 2012 at 12:29 PM, John Hunterjdh2...@gmail.com wrote:
On Fri, Jun 29, 2012 at 2:20 PM, Jim Vickroyjim.vick...@noaa.gov wrote
Hi,
On Wed, Jun 27, 2012 at 12:38 AM, Christoph Gohlke cgoh...@uci.edu wrote:
On 6/26/2012 8:13 PM, Travis Oliphant wrote:
For the main repos we use buildbot and test on:
Ubuntu Maverick 32-bit
Debian sid 64-bit
OSX 10.4 PPC
OSX 10.5 Intel
Debian wheezy PPC
Debian squeeze ARM (a
Hi,
On Thu, Jun 28, 2012 at 7:42 AM, Olivier Delalleau sh...@keba.be wrote:
+1 for a numpy-users list without dev noise.
Moderately strong vote against splitting the mailing lists into devel and user.
As we know, this list can be unhappy and distracting, but I don't
think splitting the lists
Hi,
On Thu, Jun 28, 2012 at 1:42 PM, srean srean.l...@gmail.com wrote:
In case this changes your mind (or assuages fears) just wanted to
point out that many open source projects do this. It is not about
claiming that one is more important than the other, nor does it
reinforce the idea that
Hi,
On Thu, Jun 28, 2012 at 2:30 PM, Hanno Klemm kl...@phys.ethz.ch wrote:
Am 28.06.2012 um 23:07 schrieb Matthew Brett:
Hi,
On Thu, Jun 28, 2012 at 1:42 PM, srean srean.l...@gmail.com wrote:
In case this changes your mind (or assuages fears) just wanted to
point out that many open source
401 - 500 of 1028 matches
Mail list logo
