Hi,
While cleaning up the numpy wiki start page I came across a bzr mirror
that still pointed to svn, https://launchpad.net/numpy, originally
registered by Jarrod. It would be good to either point that to git or
delete it. I couldn't see how to report or do anything about that on
Launchpad, but th
Pauli,
Thanks a lot for doing this, it helps a lot. Ilan was on another project
this morning so this helps get the merge process started faster. It looks
like it is auto-merging changes from Travis's repository because several
recent changes are moved over. I will double check, but we should be
On 11/11/10 10:21 AM, Pierre GM wrote:
> Now, we can argue over the very last point: if both a converter and a dtype
> are specified, which one should take precedence?
> You have my opinion, let's hear yours.
I say raise an exception -- it's a programmer's error -- make that clear.
-Chris
--
On Fri, 12 Nov 2010 14:37:19 -0600, Jason McCampbell wrote:
>> Sure:
>>
>>https://github.com/numpy/numpy-refactor
>>
>> I can re-sync/scrap it later on if needed, depending on what the
>> refactoring team wants to do with it.
Ok, maybe to clarify:
- That repo is already created,
- It con
Lou,
as for your confusion about where "acos()" came from:
You are right that if you do:
from math import *
and
from numpy import *
numpy will override some of the math functions, but not "acos()",
because numpy has "arccos()" function instead.
And all of this is a good reminder to not use "i
On Fri, Nov 12, 2010 at 1:37 PM, Jason McCampbell wrote:
>
>
> On Fri, Nov 12, 2010 at 10:56 AM, Pauli Virtanen wrote:
>
>> Fri, 12 Nov 2010 09:24:56 -0700, Charles R Harris wrote:
>> [clip]
>> > The teoliphant repository is usually quiet on the weekends. Would it be
>> > reasonable to make gith
On Fri, Nov 12, 2010 at 10:56 AM, Pauli Virtanen wrote:
> Fri, 12 Nov 2010 09:24:56 -0700, Charles R Harris wrote:
> [clip]
> > The teoliphant repository is usually quiet on the weekends. Would it be
> > reasonable to make github.com/numpy/numpy-refactor this weekend and ask
> > the refactor folk
Fri, 12 Nov 2010 09:24:56 -0700, Charles R Harris wrote:
[clip]
> The teoliphant repository is usually quiet on the weekends. Would it be
> reasonable to make github.com/numpy/numpy-refactor this weekend and ask
> the refactor folks to start their work there next Monday?
Sure:
https://git
From: Charles R Harris
To: Discussion of Numerical Python
Sent: Fri, November 12, 2010 10:34:58 AM
Subject: Re: [Numpy-discussion] Change in Python/Numpy numerics with Py version
2.6 ?
On Fri, Nov 12, 2010 at 8:02 AM, Lou Pecora wrote:
I ran across what see
On Thu, Nov 11, 2010 at 5:48 PM, Pauli Virtanen wrote:
> On Thu, 11 Nov 2010 16:37:53 -0600, Jason McCampbell wrote:
> [clip]
> > We will take a look at this and the script. There is also a feature in
> > git that allows two trees to be grafted together so the refactoring will
> > end up as a br
On Fri, Nov 12, 2010 at 09:58, Lou Pecora wrote:
> Thanks, Robert. I thought some math functions were replaced by numpy
> functions
> that can also operate on arrays when using from numpy import *. That's the
> reason I asked about numpy. I know I should change this.
No, we don't touch the mat
- Original Message
From: Robert Kern
To: Discussion of Numerical Python
Sent: Fri, November 12, 2010 10:39:54 AM
Subject: Re: [Numpy-discussion] Change in Python/Numpy numerics with Py version
2.6 ?
On Fri, Nov 12, 2010 at 09:02, Lou Pecora wrote:
> I ran across what seems to be a cha
On Fri, Nov 12, 2010 at 09:02, Lou Pecora wrote:
> I ran across what seems to be a change in how numerics are handled in Python
> 2.6
> or Numpy 1.3.0 or both, I'm not sure. I've recently switched from using
> Python
> 2.4 and Numpy 1.0.3 to using the Python 2.6 and Numpy 1.3.0 that comes with
On Fri, Nov 12, 2010 at 8:02 AM, Lou Pecora wrote:
> I ran across what seems to be a change in how numerics are handled in
> Python 2.6
> or Numpy 1.3.0 or both, I'm not sure. I've recently switched from using
> Python
> 2.4 and Numpy 1.0.3 to using the Python 2.6 and Numpy 1.3.0 that comes with
On 11/11/2010 09:02 PM, David Cournapeau wrote:
> On Fri, Nov 12, 2010 at 7:15 AM, Travis Oliphant
> wrote:
>
>> At the same time, the work on the .NET framework has pushed us to move more
>> of SciPy to a Cython-generated set. There are additional things I would
>> like to see SciPy improve on
I ran across what seems to be a change in how numerics are handled in Python
2.6
or Numpy 1.3.0 or both, I'm not sure. I've recently switched from using Python
2.4 and Numpy 1.0.3 to using the Python 2.6 and Numpy 1.3.0 that comes with
SAGE
which is a large mathematical package. But the issu
Fri, 12 Nov 2010 12:02:55 +0900, David Cournapeau wrote:
[clip: Python 3 on Scipy]
> I don't exactly where we are there, but Pauli and me took a look at
> scipy for python 3 at euroscipy in Paris, and I think it is mostly a
> matter of low hanging fruits. Most (all ?) changes are in the trunk
> alr
17 matches
Mail list logo
