On 24 Nov 2008, at 19:45 , Francesc Alted wrote:
> standards in computer science. For example, where Python writes:
>
> asin, acos, atan, asinh, acosh, atanh
>
> NumPy choose:
>
> arcsin, arccos, arctan, arcsinh, arccosh, arctanh
>
> So, IMHO, I think it would be better to rename the inverse
>
On Nov 24, 2008, at 5:55 PM, Jarrod Millman wrote:
> On Mon, Nov 24, 2008 at 10:45 AM, Francesc Alted
> <[EMAIL PROTECTED]> wrote:
>> So, IMHO, I think it would be better to rename the inverse
>> trigonometric
>> functions from ``arc*`` to ``a*`` prefix. Of course, in order to do
>> that cor
A Monday 24 November 2008, Jarrod Millman escrigué:
> On Mon, Nov 24, 2008 at 10:45 AM, Francesc Alted <[EMAIL PROTECTED]>
wrote:
> > So, IMHO, I think it would be better to rename the inverse
> > trigonometric functions from ``arc*`` to ``a*`` prefix. Of course,
> > in order to do that correctly
On Mon, Nov 24, 2008 at 19:29, Christopher Barker <[EMAIL PROTECTED]> wrote:
> Robert Kern wrote:
>> On Mon, Nov 24, 2008 at 18:40, Chris Barker <[EMAIL PROTECTED]> wrote:
>>> actually, it is, isn't it? a version of math.cos that works for arrays?
>>
>> No. Not at all. acos() and arccos() are the i
Robert Kern wrote:
> On Mon, Nov 24, 2008 at 18:40, Chris Barker <[EMAIL PROTECTED]> wrote:
>> actually, it is, isn't it? a version of math.cos that works for arrays?
>
> No. Not at all. acos() and arccos() are the inverse functions of cos().
argg!! total brain freeze there. Can I pretend I never
On Mon, Nov 24, 2008 at 18:40, Chris Barker <[EMAIL PROTECTED]> wrote:
> Matthew Brett wrote:
>> numpy.asum numpy.arange numpy.amax etc all have the intended meaning
>> of 'a-for-array-version-of-function'. This obviously isn't the case
>> for 'acos'.
>
> actually, it is, isn't it? a version of m
Matthew Brett wrote:
> numpy.asum numpy.arange numpy.amax etc all have the intended meaning
> of 'a-for-array-version-of-function'. This obviously isn't the case
> for 'acos'.
actually, it is, isn't it? a version of math.cos that works for arrays?
But anyway, if we had it to do all over again,
On Mon, Nov 24, 2008 at 17:13, Charles R Harris
<[EMAIL PROTECTED]> wrote:
> Maybe we could push all the changes off to a Numpy release compatible with
> Python 3.0. Folks will expect a certain amount of hassle when making that
> switch.
Guido, et al., have specifically asked that projects not do
Hi,
I think this change could be confusing.
numpy.asum numpy.arange numpy.amax etc all have the intended meaning
of 'a-for-array-version-of-function'. This obviously isn't the case
for 'acos'. Explaining the difference could be painful.
Best,
Matthew
_
On Mon, Nov 24, 2008 at 4:09 PM, Charles R Harris <[EMAIL PROTECTED]
> wrote:
>
>
> On Mon, Nov 24, 2008 at 3:55 PM, Jarrod Millman <[EMAIL PROTECTED]>wrote:
>
>> On Mon, Nov 24, 2008 at 10:45 AM, Francesc Alted <[EMAIL PROTECTED]>
>> wrote:
>> > So, IMHO, I think it would be better to rename the
I agree with Jon here. I can see plenty of motivation for adding the
names asin, etc., but there really isn't a need to remove the current
versions, and it will just introduce compatibility issues when someone
tries to run code written with NumPy 1.x using a NumPy 2.x
installation for even the simp
On Mon, Nov 24, 2008 at 3:55 PM, Jarrod Millman <[EMAIL PROTECTED]>wrote:
> On Mon, Nov 24, 2008 at 10:45 AM, Francesc Alted <[EMAIL PROTECTED]>
> wrote:
> > So, IMHO, I think it would be better to rename the inverse trigonometric
> > functions from ``arc*`` to ``a*`` prefix. Of course, in order
On Mon, Nov 24, 2008 at 10:45 AM, Francesc Alted <[EMAIL PROTECTED]> wrote:
> So, IMHO, I think it would be better to rename the inverse trigonometric
> functions from ``arc*`` to ``a*`` prefix. Of course, in order to do
> that correctly, one should add the new names and add a
> ``DeprecationWarni
On Mon, Nov 24, 2008 at 3:00 PM, David Warde-Farley <[EMAIL PROTECTED]>wrote:
>
> On 24-Nov-08, at 4:22 PM, Gabriel Gellner wrote:
>
> >> asin(1j) raises an exception, arcsin doesn't. They are *different*
> >> functions, hence the names.
> >>
> > Yet:
> >
> type(np.sin(1)) == type(math.sin(1)
On 24-Nov-08, at 4:22 PM, Gabriel Gellner wrote:
>> asin(1j) raises an exception, arcsin doesn't. They are *different*
>> functions, hence the names.
>>
> Yet:
>
type(np.sin(1)) == type(math.sin(1))
> False
In fact, this goes for every single function listed in the math
module's docs, exc
On Mon, Nov 24, 2008 at 09:00:48PM +0100, Jon Wright wrote:
> There is resistance. Please don't remove the old names. Also note that
> your proposed change will alter people's code in subtle, but potentially
> very "interesting" ways:
> >>> from math import *
> >>> from numpy import *
> >>> type
> There is resistance. Please don't remove the old names. Also note that
> your proposed change will alter people's code in subtle, but potentially
> very "interesting" ways:
>
> >>> from math import *
> >>> from numpy import *
> >>> type(arcsin(1)) is type(asin(1))
> False
> >>> from numpy impo
On Mon, Nov 24, 2008 at 14:00, Jon Wright <[EMAIL PROTECTED]> wrote:
> I have the feeling the only times I ever write to this list is to say
> "please don't change the API". So, here I am again, "please don't change
> the API". This is a cosmetic change whose only effect seems to be to
> have every
Eric Firing wrote:
> Francesc Alted wrote:
>
>> So, IMHO, I think it would be better to rename the inverse trigonometric
>> functions from ``arc*`` to ``a*`` prefix.
>
> +1
> I have stumbled over this myself. If there is resistance to removing
-1
There is resistance. Please don't remove the o
Francesc Alted wrote:
> So, IMHO, I think it would be better to rename the inverse trigonometric
> functions from ``arc*`` to ``a*`` prefix. Of course, in order to do
> that correctly, one should add the new names and add a
> ``DeprecationWarning`` informing that people should start to use the
On Mon, Nov 24, 2008 at 07:45:56PM +0100, Francesc Alted wrote:
> Hi,
>
> After dealing with another issue, I realized that the names of inverse
> trigonometrical/hyperbolic functions in NumPy don't follow the main
> standards in computer science. For example, where Python writes:
>
> asin, ac
Francesc Alted wrote:
> Hi,
>
> After dealing with another issue, I realized that the names of inverse
> trigonometrical/hyperbolic functions in NumPy don't follow the main
> standards in computer science. For example, where Python writes:
>
> asin, acos, atan, asinh, acosh, atanh
>
> NumPy c
Hi,
After dealing with another issue, I realized that the names of inverse
trigonometrical/hyperbolic functions in NumPy don't follow the main
standards in computer science. For example, where Python writes:
asin, acos, atan, asinh, acosh, atanh
NumPy choose:
arcsin, arccos, arctan, arcsinh,
23 matches
Mail list logo
