On Fri, Aug 31, 2012 at 5:56 PM, Mark Wiebe wrote:
> On Fri, Aug 31, 2012 at 5:35 PM, Ondřej Čertík
> wrote:
>>
>> Hi Dag,
>>
>> On Fri, Aug 31, 2012 at 4:22 AM, Dag Sverre Seljebotn
>> wrote:
>> > On 08/31/2012 09:03 AM, Ondřej Čertík wrote:
>> >> Hi,
>> >>
>> >> There is segfault reported here
On Fri, Aug 31, 2012 at 5:35 PM, Ondřej Čertík wrote:
> Hi Dag,
>
> On Fri, Aug 31, 2012 at 4:22 AM, Dag Sverre Seljebotn
> wrote:
> > On 08/31/2012 09:03 AM, Ondřej Čertík wrote:
> >> Hi,
> >>
> >> There is segfault reported here:
> >>
> >> http://projects.scipy.org/numpy/ticket/1588
> >>
> >> I
Hi Dag,
On Fri, Aug 31, 2012 at 4:22 AM, Dag Sverre Seljebotn
wrote:
> On 08/31/2012 09:03 AM, Ondřej Čertík wrote:
>> Hi,
>>
>> There is segfault reported here:
>>
>> http://projects.scipy.org/numpy/ticket/1588
>>
>> I've managed to isolate the problem and even provide a simple patch,
>> that fi
01.09.2012 00:08, Ognen Duzlevski kirjoitti:
[clip]
> I personally think moving away from Trac (which IMHO is bloated and
> awkward in addition to having a very weird way of being administered)
> would be a better idea.
Yes, moving away from Trac is planned, both for Numpy and Scipy. Also
agreed o
On Fri, Aug 31, 2012 at 11:35 AM, Pauli Virtanen wrote:
> Ondřej Čertík gmail.com> writes:
>> When I access tickets, for example:
>>
>> http://projects.scipy.org/numpy/ticket/2185
>>
>> then sometimes I get:
>>
>> Trac detected an internal error:
>> OperationalError: database is locked
>>
>> For
On Fri, Aug 31, 2012 at 7:17 PM, Ondřej Čertík wrote:
> If you could create issues at github: https://github.com/numpy/numpy/issues
> that would be great. If you have time, also with some info about the platform
> and how to reproduce it. Or at least a link to the build logs.
I've reported it her
Ondrej,
Just submitted the following pull request for this:
https://github.com/numpy/numpy/pull/401
-Jay
On Fri, Aug 31, 2012 at 12:09 PM, Ondřej Čertík wrote:
> On Fri, Aug 31, 2012 at 6:15 AM, Jay Bourque
> wrote:
> > Ondrej,
> >
> > Sorry for the delay in getting back to this. I have some
Ond??ej ??ert??k wrote:
> > python3.2-dbg: numpy/core/src/multiarray/common.c:161:
> > PyArray_DTypeFromObjectHelper: Assertion
> > `((PyObject*)(temp))->ob_type))->tp_flags & ((1L<<27))) != 0)'
>
> If you could create issues at github: https://github.com/numpy/numpy/issues
> that would be gr
On Fri, Aug 31, 2012 at 10:26 AM, Charles R Harris
wrote:
>
>
> On Fri, Aug 31, 2012 at 11:10 AM, Ondřej Čertík
[...]
>> Yes, I don't have commit rights nor the rights to close tickets.
>>
>
> OK, I gave commit rights to you. Someone else (Pauli) will need to give you
> rights to close tickets.
On Fri, Aug 31, 2012 at 11:10 AM, Ondřej Čertík wrote:
> On Fri, Aug 31, 2012 at 9:27 AM, Charles R Harris
> wrote:
> >
> >
> > On Thu, Aug 30, 2012 at 10:47 PM, Ondřej Čertík >
> > wrote:
> >>
> >> Hi,
> >>
> >> I am keeping track of all issues that need to be done for the 1.7.0
> >> release he
Hi Sandro,
On Fri, Aug 31, 2012 at 6:18 AM, Sandro Tosi wrote:
> Hello,
>
> On Tue, Aug 21, 2012 at 6:24 PM, Ondřej Čertík
> wrote:
>> Hi,
>>
>> I'm pleased to announce the availability of the first beta release of
>> NumPy 1.7.0b1.
>
> I've just uploaded it to Debian experimental, so we can gi
On Fri, Aug 31, 2012 at 9:35 AM, Pauli Virtanen wrote:
> Ondřej Čertík gmail.com> writes:
>> When I access tickets, for example:
>>
>> http://projects.scipy.org/numpy/ticket/2185
>>
>> then sometimes I get:
>>
>> Trac detected an internal error:
>> OperationalError: database is locked
>>
>> For e
On Fri, Aug 31, 2012 at 9:27 AM, Charles R Harris
wrote:
>
>
> On Thu, Aug 30, 2012 at 10:47 PM, Ondřej Čertík
> wrote:
>>
>> Hi,
>>
>> I am keeping track of all issues that need to be done for the 1.7.0
>> release here:
>>
>> https://github.com/numpy/numpy/issues/396
>>
>> If you have trac and g
On Fri, Aug 31, 2012 at 6:15 AM, Jay Bourque wrote:
> Ondrej,
>
> Sorry for the delay in getting back to this. I have some free time today to
> get this resolved if you haven't already fixed it.
I haven't. If you can look at it, that would be absolutely awesome.
If you don't manage to fix it, if
Ondřej Čertík gmail.com> writes:
> When I access tickets, for example:
>
> http://projects.scipy.org/numpy/ticket/2185
>
> then sometimes I get:
>
> Trac detected an internal error:
> OperationalError: database is locked
>
> For example yesterday. A refresh in about a minute fixed the problem.
On Thu, Aug 30, 2012 at 10:47 PM, Ondřej Čertík wrote:
> Hi,
>
> I am keeping track of all issues that need to be done for the 1.7.0
> release here:
>
> https://github.com/numpy/numpy/issues/396
>
> If you have trac and github push access, here is how you can help (by
> closing/merging):
>
> Issue
Hello,
On Tue, Aug 21, 2012 at 6:24 PM, Ondřej Čertík wrote:
> Hi,
>
> I'm pleased to announce the availability of the first beta release of
> NumPy 1.7.0b1.
I've just uploaded it to Debian experimental, so we can give it a run
while in freeze. Some of the buildds are already building[1] the
pac
Ondrej,
Sorry for the delay in getting back to this. I have some free time today to
get this resolved if you haven't already fixed it.
-Jay
On Wed, Aug 29, 2012 at 7:19 PM, Ondřej Čertík wrote:
> Jay,
>
> On Mon, Aug 20, 2012 at 12:40 PM, Ondřej Čertík
> wrote:
> > On Wed, Jul 25, 2012 at 10:2
On 08/31/2012 09:03 AM, Ondřej Čertík wrote:
> Hi,
>
> There is segfault reported here:
>
> http://projects.scipy.org/numpy/ticket/1588
>
> I've managed to isolate the problem and even provide a simple patch,
> that fixes it here:
>
> https://github.com/numpy/numpy/issues/398
>
> however the patch
Hi,
I'm using numpy 1.6.1 on Ubuntu 12.04.1 LTS.
A code that used to work with an older version of numpy now fails with an error.
Were there any changes in the way inplace operations like +=, *=, etc.
work on arrays with non-standard strides?
For the script:
--- start of code ---
impor
Hi,
re: valgrind - to get better results you might try the suggestions from:
http://svn.python.org/projects/python/trunk/Misc/README.valgrind
Richard
On 31 August 2012 09:03, Ondřej Čertík wrote:
> Hi,
>
> There is segfault reported here:
>
> http://projects.scipy.org/numpy/ticket/1588
>
> I'v
Hi,
There is segfault reported here:
http://projects.scipy.org/numpy/ticket/1588
I've managed to isolate the problem and even provide a simple patch,
that fixes it here:
https://github.com/numpy/numpy/issues/398
however the patch simply doesn't decrease the proper reference, so it
might leak.
22 matches
Mail list logo