ti, 2009-12-08 kello 21:52 +0100, Dag Sverre Seljebotn kirjoitti:
[clip]
> How about this:
> - Cache/store the format string in a bytes object in a global
> WeakRefKeyDict (?), keyed by dtype
> - The array holds a ref to the dtype, and the Py_buffer holds a ref to
> the array (through the ob
On Tue, Dec 8, 2009 at 14:52, Dag Sverre Seljebotn
wrote:
> Robert Kern wrote:
>> On Tue, Dec 8, 2009 at 12:38, Pauli Virtanen wrote:
>>> - We need to cache the buffer protocol format string somewhere,
>>> if we do not want to regenerate it on each buffer acquisition.
>>
>> My suspicion is that
Robert Kern wrote:
> On Tue, Dec 8, 2009 at 12:38, Pauli Virtanen wrote:
>> ti, 2009-12-08 kello 12:14 -0600, Robert Kern kirjoitti:
>>> On Tue, Dec 8, 2009 at 12:08, Pauli Virtanen wrote:
ke, 2009-12-09 kello 02:47 +0900, David Cournapeau kirjoitti:
[clip]
> Of course, this does no
On Tue, Dec 8, 2009 at 12:38, Pauli Virtanen wrote:
> ti, 2009-12-08 kello 12:14 -0600, Robert Kern kirjoitti:
>> On Tue, Dec 8, 2009 at 12:08, Pauli Virtanen wrote:
>> > ke, 2009-12-09 kello 02:47 +0900, David Cournapeau kirjoitti:
>> > [clip]
>> >> Of course, this does not prevent from applying
ti, 2009-12-08 kello 12:14 -0600, Robert Kern kirjoitti:
> On Tue, Dec 8, 2009 at 12:08, Pauli Virtanen wrote:
> > ke, 2009-12-09 kello 02:47 +0900, David Cournapeau kirjoitti:
> > [clip]
> >> Of course, this does not prevent from applying your suggested change -
> >> I don't understand why you wa
On Tue, Dec 8, 2009 at 12:08, Pauli Virtanen wrote:
> ke, 2009-12-09 kello 02:47 +0900, David Cournapeau kirjoitti:
> [clip]
>> Of course, this does not prevent from applying your suggested change -
>> I don't understand why you want to add it to 1.4.0, though. 1.4.0 does
>> not break the ABI comp
ke, 2009-12-09 kello 02:47 +0900, David Cournapeau kirjoitti:
[clip]
> Of course, this does not prevent from applying your suggested change -
> I don't understand why you want to add it to 1.4.0, though. 1.4.0 does
> not break the ABI compared to 1.3.0. Or is it "just" to avoid the
> cython issue t
On Wed, Dec 9, 2009 at 2:37 AM, Pauli Virtanen wrote:
> ke, 2009-12-09 kello 02:28 +0900, David Cournapeau kirjoitti:
> [clip]
>> It seems that it is partly a cython problem. If py3k can be done for
>> numpy 1.5, I wonder if we should focus on making incompatible numpy
>> 1.6 (or 2.0 :) ), with an
On Tue, Dec 8, 2009 at 11:28, David Cournapeau wrote:
> On Wed, Dec 9, 2009 at 2:02 AM, Pauli Virtanen wrote:
>> Sun, 06 Dec 2009 14:53:58 +0100, Gael Varoquaux wrote:
>>> I have a lot of code that has stopped working with my latest SVN pull to
>>> numpy.
>>>
>>> * Some compiled code yields an er
ke, 2009-12-09 kello 02:28 +0900, David Cournapeau kirjoitti:
[clip]
> It seems that it is partly a cython problem. If py3k can be done for
> numpy 1.5, I wonder if we should focus on making incompatible numpy
> 1.6 (or 2.0 :) ), with an emphasis on making the C api more robust
> about those change
On Wed, Dec 09, 2009 at 02:28:46AM +0900, David Cournapeau wrote:
> As numpy becomes more and more used as a basic for so many softwares,
> I feel like the current situation is hurting numpy users quite badly.
> Maybe I am overestimate the problem, though ?
I think you are right. It is going to hu
On Wed, Dec 9, 2009 at 2:02 AM, Pauli Virtanen wrote:
> Sun, 06 Dec 2009 14:53:58 +0100, Gael Varoquaux wrote:
>> I have a lot of code that has stopped working with my latest SVN pull to
>> numpy.
>>
>> * Some compiled code yields an error looking like (from memory):
>>
>> "incorrect type 'num
ti, 2009-12-08 kello 12:12 -0500, Darren Dale kirjoitti:
> On Tue, Dec 8, 2009 at 12:02 PM, Pauli Virtanen wrote:
> > Sun, 06 Dec 2009 14:53:58 +0100, Gael Varoquaux wrote:
> >> I have a lot of code that has stopped working with my latest SVN pull to
> >> numpy.
> >>
> >> * Some compiled code yiel
On Tue, Dec 8, 2009 at 12:02 PM, Pauli Virtanen wrote:
> Sun, 06 Dec 2009 14:53:58 +0100, Gael Varoquaux wrote:
>> I have a lot of code that has stopped working with my latest SVN pull to
>> numpy.
>>
>> * Some compiled code yields an error looking like (from memory):
>>
>> "incorrect type 'nu
Sun, 06 Dec 2009 14:53:58 +0100, Gael Varoquaux wrote:
> I have a lot of code that has stopped working with my latest SVN pull to
> numpy.
>
> * Some compiled code yields an error looking like (from memory):
>
> "incorrect type 'numpy.ndarray'"
This, by the way, also affects the 1.4.x branch
15 matches
Mail list logo
