On Thu, Jun 11, 2009 at 15:33, Pierre GM wrote:
>
> On Jun 11, 2009, at 3:47 PM, Robert Kern wrote:
>
>> On Thu, Jun 11, 2009 at 14:37, Pierre GM wrote:
>>> Oh, just another question: why trying to put datetime and timedelta
>>> in
>>> the type ordering ? My understanding is that underneath, they'
On Jun 11, 2009, at 3:47 PM, Robert Kern wrote:
> On Thu, Jun 11, 2009 at 14:37, Pierre GM wrote:
>>
>> On Jun 11, 2009, at 3:07 PM, Travis Oliphant wrote:
>>
BTW, what is the metadata that is going to be added to the types?
What purpose does it serve?
>>>
>>> In the date-time case, it
On Thu, Jun 11, 2009 at 14:37, Pierre GM wrote:
>
> On Jun 11, 2009, at 3:07 PM, Travis Oliphant wrote:
>
>>> BTW, what is the metadata that is going to be added to the types?
>>> What purpose does it serve?
>>
>> In the date-time case, it holds what frequency the integer in the
>> data-
>> type re
On Jun 11, 2009, at 3:07 PM, Travis Oliphant wrote:
>> BTW, what is the metadata that is going to be added to the types?
>> What purpose does it serve?
>
> In the date-time case, it holds what frequency the integer in the
> data-
> type represents.There will only be 2 new static data-types.
On Thu, Jun 11, 2009 at 1:07 PM, Travis Oliphant wrote:
>
> In the date-time case, it holds what frequency the integer in the data-
> type represents.There will only be 2 new static data-types.
> "Datetime" and "Timedelta" that use 8 bytes each.
>
> What those 8 bytes represent will be dete
On Jun 11, 2009, at 1:18 PM, Robert Kern wrote:
> This line from generate_umath.py?
>
> all = '?bBhHiIlLqQtTfdgFDGO'
Oh, I don't think it's a good idea to use "T" and "t" for date-time.
In the struct module this mean "struct" and "bit" respectively.
I propose "M" and "m"
-Travis
On Thu, Jun 11, 2009 at 1:07 PM, Travis Oliphant wrote:
>
> On Jun 11, 2009, at 1:44 PM, Charles R Harris wrote:
>
> >
> > The implementation of PyArray_CanCastSafely illustrates two other
> > points that bother me.
> >
> > 1) The rules are encoded in the program logic. This makes them
> > diffic
On Jun 11, 2009, at 1:44 PM, Charles R Harris wrote:
>
> The implementation of PyArray_CanCastSafely illustrates two other
> points that bother me.
>
> 1) The rules are encoded in the program logic. This makes them
> difficult to find or to see what they are and requires editing the
> code
--- On Thu, 6/11/09, Skipper Seabold wrote:
> > Thanks, both for your kind words and for the patch; I
> don't suppose I could prevail upon you to be Team Lead for
> doc-ing numpy.finacial?
> >
> > DG
> >
>
> Sure why not.
Great! I'm done editing the Wiki for a bit if you wanna go ahead and ad
On Thu, Jun 11, 2009 at 13:44, Charles R
Harris wrote:
>
>
> On Thu, Jun 11, 2009 at 12:18 PM, Robert Kern wrote:
>>
>> On Thu, Jun 11, 2009 at 13:06, Charles R
>> Harris wrote:
>> >
>> >
>> > On Thu, Jun 11, 2009 at 11:47 AM, Robert Kern
>> > wrote:
>> >>
>> >> On Thu, Jun 11, 2009 at 12:39, Cha
On Thu, Jun 11, 2009 at 12:18 PM, Robert Kern wrote:
> On Thu, Jun 11, 2009 at 13:06, Charles R
> Harris wrote:
> >
> >
> > On Thu, Jun 11, 2009 at 11:47 AM, Robert Kern
> wrote:
> >>
> >> On Thu, Jun 11, 2009 at 12:39, Charles R
> >> Harris wrote:
> >> >
> >> >
> >> > On Thu, Jun 11, 2009 at 11
On Thu, Jun 11, 2009 at 13:06, Charles R
Harris wrote:
>
>
> On Thu, Jun 11, 2009 at 11:47 AM, Robert Kern wrote:
>>
>> On Thu, Jun 11, 2009 at 12:39, Charles R
>> Harris wrote:
>> >
>> >
>> > On Thu, Jun 11, 2009 at 11:34 AM, Robert Kern
>> > wrote:
>> >>
>> >> On Thu, Jun 11, 2009 at 12:29, Cha
On Thu, Jun 11, 2009 at 11:47 AM, Robert Kern wrote:
> On Thu, Jun 11, 2009 at 12:39, Charles R
> Harris wrote:
> >
> >
> > On Thu, Jun 11, 2009 at 11:34 AM, Robert Kern
> wrote:
> >>
> >> On Thu, Jun 11, 2009 at 12:29, Charles R
> >> Harris wrote:
> >> > Oh, and slipping the new types in betwee
On Thu, Jun 11, 2009 at 12:39, Charles R
Harris wrote:
>
>
> On Thu, Jun 11, 2009 at 11:34 AM, Robert Kern wrote:
>>
>> On Thu, Jun 11, 2009 at 12:29, Charles R
>> Harris wrote:
>> > Oh, and slipping the new types in between 64 bit integers and floats is
>> > a
>> > bit iffy.
>>
>> Where, specific
On Thu, Jun 11, 2009 at 11:34 AM, Robert Kern wrote:
> On Thu, Jun 11, 2009 at 12:29, Charles R
> Harris wrote:
> > Oh, and slipping the new types in between 64 bit integers and floats is a
> > bit iffy.
>
> Where, specifically? There are several linear orders of types in
> numpy. I tried to be c
On Thu, Jun 11, 2009 at 12:29, Charles R
Harris wrote:
> Oh, and slipping the new types in between 64 bit integers and floats is a
> bit iffy.
Where, specifically? There are several linear orders of types in
numpy. I tried to be careful to do the right thing in each. The enum
numbers are after NPY
On Thu, Jun 11, 2009 at 1:23 PM, David Goldsmith wrote:
>
> Thanks, both for your kind words and for the patch; I don't suppose I could
> prevail upon you to be Team Lead for doc-ing numpy.finacial?
>
> DG
>
Sure why not.
___
Numpy-discussion mailing li
On Thu, Jun 11, 2009 at 10:29 AM, Travis Oliphant wrote:
>
> On Jun 10, 2009, at 11:18 PM, Charles R Harris wrote:
>
> Hi Travis,
>
> I looked through the recent commits to the datetime branch and, as I'm
> working on cleaning up arraytypes I would appreciate it if you can merge up
> your changes
Thanks, both for your kind words and for the patch; I don't suppose I could
prevail upon you to be Team Lead for doc-ing numpy.finacial?
DG
--- On Thu, 6/11/09, Skipper Seabold wrote:
> > OK, I concede defeat: if it is the wisdom of the PTB
> that numpy.financial be retained, I will stop mess
On Thu, Jun 11, 2009 at 10:29 AM, Travis Oliphant wrote:
>
> On Jun 10, 2009, at 11:18 PM, Charles R Harris wrote:
>
> Hi Travis,
>
> I looked through the recent commits to the datetime branch and, as I'm
> working on cleaning up arraytypes I would appreciate it if you can merge up
> your changes
On Mon, Jun 8, 2009 at 11:02 AM, David Cournapeau <
da...@ar.media.kyoto-u.ac.jp> wrote:
> Isn't it true for any general framework who enjoys some popularity :)
Yup :)
I think there are cases where gradient methods are not applicable
> (latent models where the complete data Y cannot be split in
On Thu, Jun 11, 2009 at 11:58 AM, David Cournapeau wrote:
> Ignore diagnose.py for the time being - what does f2py says ?
running build
running config_fc
running build_src
building extension "ese" sources
f2py options: []
adding '/tmp/tmpFE_lPq/src.macosx-10.5-i386-2.5/fortranobject.c' to source
On Wed, Jun 10, 2009 at 1:00 AM, David Goldsmith wrote:
>
> --- On Tue, 6/9/09, Skipper Seabold wrote:
>
>> I have implemented the ipmt and ppmt functions that were
>> "not
>> implemented" in numpy.lib.financial as well as written some
>> tests.
>
> Thanks!
>
>> ipmt is one of the functions where
On Fri, Jun 12, 2009 at 12:56 AM, Samir Unni wrote:
> On Wed, Jun 10, 2009 at 8:32 PM, David Cournapeau wrote:
>> On Thu, Jun 11, 2009 at 5:04 AM, Samir Unni wrote:
>>> On Wed, Jun 10, 2009 at 2:59 PM, Adam Mercer wrote:
On Wed, Jun 10, 2009 at 12:44, Samir Unni wrote:
> I'm trying to
On Wed, Jun 10, 2009 at 8:32 PM, David Cournapeau wrote:
> On Thu, Jun 11, 2009 at 5:04 AM, Samir Unni wrote:
>> On Wed, Jun 10, 2009 at 2:59 PM, Adam Mercer wrote:
>>> On Wed, Jun 10, 2009 at 12:44, Samir Unni wrote:
>>>
I'm trying to use F2PY on Mac OS 10.5 with G95, but I'm getting the
On Jun 10, 2009, at 11:18 PM, Charles R Harris wrote:
Hi Travis,
I looked through the recent commits to the datetime branch and, as
I'm working on cleaning up arraytypes I would appreciate it if you
can merge up your changes there as soon as possible to minimize
conflicts. Also, this cha
Hello,
I just came across 'all' and 'alltrue' functions in fromnumeric.py
They are one and same.
IMHO,
alltrue = all
would be sufficient.
Regards
___
Shivaraj
--
Regards
___
Shivaraj
___
Numpy-discussion mailing list
Numpy-disc
27 matches
Mail list logo
