On Fri, Oct 16, 2009 at 9:35 PM, Travis Oliphant wrote:
>
> On Oct 15, 2009, at 11:40 AM, Michael Droettboom wrote:
>
> I recently committed a regression test and bugfix for object pointers in
> record arrays of unaligned size (meaning where each record is not a
> multiple of sizeof(PyObject **)).
On Oct 15, 2009, at 11:40 AM, Michael Droettboom wrote:
I recently committed a regression test and bugfix for object
pointers in
record arrays of unaligned size (meaning where each record is not a
multiple of sizeof(PyObject **)).
For example:
a1 = np.zeros((10,), dtype=[('o', 'O'),
Robert Cimrman ntc.zcu.cz> writes:
>
> Hi Martin,
>
> thanks for your ideas and contribution.
>
> A few notes: I would let intersect1d as it is, and created a new function with
another name for that (any
> proposals?). Considering that most of arraysetops functions are based on sort,
and in pa
On Oct 16, 2009, at 8:29 AM, Skipper Seabold wrote:
> Great work! I am especially glad to see the better documentation on
> missing values, as I didn't fully understand how to do this. A few
> small comments and a small attached diff with a few nitpicking
> grammatical changes and some of what'
Francesc Alted skrev:
> The response is clear: avoid memcpy() if you can. It is true that memcpy()
> performance has improved quite a lot in latest gcc (it has been quite good in
> Win versions since many years ago), but working with data in-place (i.e.
> avoiding a memory copy) is always faste
On 10/16/2009 07:53 AM, Pauli Virtanen wrote:
> Fri, 16 Oct 2009 12:07:10 +0200, Francesc Alted wrote:
> [clip]
>
>> IMO, NumPy can be improved for unaligned data handling. For example,
>> Numexpr is using this small snippet:
>>
>> from cpuinfo import cpu
>> if cpu.is_AMD() or cpu.is_Intel():
On Thu, Oct 15, 2009 at 7:08 PM, Pierre GM wrote:
> All,
> Here's a first draft for the documentation of np.genfromtxt.
> It took me longer than I thought, but that way I uncovered and fix some
> bugs.
> Please send me your comments/reviews/etc
> I count especially on our documentation specialist
A Friday 16 October 2009 14:02:03 David Cournapeau escrigué:
> On Fri, Oct 16, 2009 at 8:53 PM, Pauli Virtanen wrote:
> > Fri, 16 Oct 2009 12:07:10 +0200, Francesc Alted wrote:
> > [clip]
> >
> >> IMO, NumPy can be improved for unaligned data handling. For example,
> >> Numexpr is using this smal
On Fri, Oct 16, 2009 at 8:53 PM, Pauli Virtanen wrote:
> Fri, 16 Oct 2009 12:07:10 +0200, Francesc Alted wrote:
> [clip]
>> IMO, NumPy can be improved for unaligned data handling. For example,
>> Numexpr is using this small snippet:
>>
>> from cpuinfo import cpu
>> if cpu.is_AMD() or cpu.is_Intel
Fri, 16 Oct 2009 12:07:10 +0200, Francesc Alted wrote:
[clip]
> IMO, NumPy can be improved for unaligned data handling. For example,
> Numexpr is using this small snippet:
>
> from cpuinfo import cpu
> if cpu.is_AMD() or cpu.is_Intel():
> is_cpu_amd_intel = True
> else:
> is_cpu_amd_intel
A Thursday 15 October 2009 19:00:04 Charles R Harris escrigué:
> > So, how to fix this?
> >
> > One obvious workaround is for users to pass "align=True" to the dtype
> > constructor. This works if the dtype descriptor is a dictionary or
> > comma-separated string. Is there a reason it couldn't be
Hi Martin,
thanks for your ideas and contribution.
A few notes: I would let intersect1d as it is, and created a new function with
another name for that (any proposals?). Considering that most of arraysetops
functions are based on sort, and in particular here that an intersection array
is (usua
Fri, 16 Oct 2009 00:23:34 -0400, josef.pktd wrote:
[clip]
>> This seems exceedingly odd. Does anyone know _how_ we violated the ToS?
>
> adult material on front page
>
> Who's the owner? Creating a new group would require a different name,
> since the old name is blocked, I tried.
Maybe it's bes
13 matches
Mail list logo
