On Tue, Dec 29, 2009 at 2:00 AM, Gökhan Sever wrote:
>
> One interesting thing I have noticed while installing the numpy from the
> source is that numpy dependent libraries must be re-installed and this must
> be a clean re-install.
This is expected if you build libraries against dev versions of
On Mon, Dec 28, 2009 at 2:30 PM, Gökhan Sever wrote:
>
>
> On Mon, Dec 28, 2009 at 12:15 PM, Gökhan Sever wrote:
>
>>
>>
>> On Mon, Dec 28, 2009 at 11:16 AM, Gökhan Sever wrote:
>>
>>>
>>>
>>> On Mon, Dec 28, 2009 at 11:07 AM, Robert Kern wrote:
>>>
On Mon, Dec 28, 2009 at 11:00, Gökhan Seve
On Mon, Dec 28, 2009 at 12:15 PM, Gökhan Sever wrote:
>
>
> On Mon, Dec 28, 2009 at 11:16 AM, Gökhan Sever wrote:
>
>>
>>
>> On Mon, Dec 28, 2009 at 11:07 AM, Robert Kern wrote:
>>
>>> On Mon, Dec 28, 2009 at 11:00, Gökhan Sever
>>> wrote:
>>>
>>> > One interesting thing I have noticed while inst
On Mon, Dec 28, 2009 at 11:16 AM, Gökhan Sever wrote:
>
>
> On Mon, Dec 28, 2009 at 11:07 AM, Robert Kern wrote:
>
>> On Mon, Dec 28, 2009 at 11:00, Gökhan Sever
>> wrote:
>>
>> > One interesting thing I have noticed while installing the numpy from the
>> > source is that numpy dependent librarie
On Mon, Dec 28, 2009 at 11:07 AM, Robert Kern wrote:
> On Mon, Dec 28, 2009 at 11:00, Gökhan Sever wrote:
>
> > One interesting thing I have noticed while installing the numpy from the
> > source is that numpy dependent libraries must be re-installed and this
> must
> > be a clean re-install. Fo
On Mon, Dec 28, 2009 at 11:00, Gökhan Sever wrote:
> One interesting thing I have noticed while installing the numpy from the
> source is that numpy dependent libraries must be re-installed and this must
> be a clean re-install. For instance I can't import some matplotlib and scipy
> modules with
On Mon, Dec 28, 2009 at 10:31 AM, Gökhan Sever wrote:
>
>
> On Sat, Dec 26, 2009 at 6:09 PM, David Cournapeau wrote:
>
>> On Sun, Dec 27, 2009 at 6:19 AM, Gökhan Sever
>> wrote:
>>
>> >
>> > For the develop, it is one of easiest ways to catch up the bug-fixes
>> even
>> > though I don't work on t
On Sat, Dec 26, 2009 at 6:09 PM, David Cournapeau wrote:
> On Sun, Dec 27, 2009 at 6:19 AM, Gökhan Sever
> wrote:
>
> >
> > For the develop, it is one of easiest ways to catch up the bug-fixes even
> > though I don't work on the source directly. So far besides a few glitches
> it
> > was always w
On Sun, Dec 27, 2009 at 6:19 AM, Gökhan Sever wrote:
>
> For the develop, it is one of easiest ways to catch up the bug-fixes even
> though I don't work on the source directly. So far besides a few glitches it
> was always working. I also install scipy, ipython, matplotlib, sympy and all
> other
On Sat, Dec 26, 2009 at 4:15 PM, Charles R Harris wrote:
>
>
> On Sat, Dec 26, 2009 at 2:19 PM, Gökhan Sever wrote:
>
>>
>>
>> On Thu, Dec 24, 2009 at 4:57 PM, David Cournapeau wrote:
>>
>>> On Wed, Dec 23, 2009 at 1:41 AM, Gökhan Sever
>>> wrote:
>>> >
>>> >
>>> > On Tue, Dec 22, 2009 at 9:05 A
On Sat, Dec 26, 2009 at 2:19 PM, Gökhan Sever wrote:
>
>
> On Thu, Dec 24, 2009 at 4:57 PM, David Cournapeau wrote:
>
>> On Wed, Dec 23, 2009 at 1:41 AM, Gökhan Sever
>> wrote:
>> >
>> >
>> > On Tue, Dec 22, 2009 at 9:05 AM, David Cournapeau
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> I have just r
On Thu, Dec 24, 2009 at 4:57 PM, David Cournapeau wrote:
> On Wed, Dec 23, 2009 at 1:41 AM, Gökhan Sever
> wrote:
> >
> >
> > On Tue, Dec 22, 2009 at 9:05 AM, David Cournapeau
> > wrote:
> >>
> >> Hi,
> >>
> >> I have just released the 2nd release candidate for numpy 1.4.0, which
> >> fixes a fe
On Wed, Dec 23, 2009 at 11:54 PM, Bruce Southey wrote:
> Some of the Python 3.1 features have been backported to Python 2.7 which
> will help with some of the porting to Python 3. For that reason, I would
> suggest that release notes indicate that Python 2.7 support is
> experimental - especially
On Wed, Dec 23, 2009 at 1:41 AM, Gökhan Sever wrote:
>
>
> On Tue, Dec 22, 2009 at 9:05 AM, David Cournapeau
> wrote:
>>
>> Hi,
>>
>> I have just released the 2nd release candidate for numpy 1.4.0, which
>> fixes a few critical bugs founds since the RC1. Tarballs and binary
>> installers for nump
On 12/22/2009 09:53 PM, David Cournapeau wrote:
> On Wed, Dec 23, 2009 at 12:50 AM, Bruce Southey wrote:
>
>
>> This still crashes Python 2.7 with the test_multiarray.TestIO.test_ascii.
>>
> Could you file a ticket next time ? I could not follow closely the
> discussion the last week or
On Wed, Dec 23, 2009 at 4:40 AM, Pauli Virtanen wrote:
> I suppose raising an exception requires ownership of GIL.
I am curious: how did you know it was related to the GIL ? When I
tried debugging the issue, I could not tell whereas this was a problem
with python 2.7 or with numpy, and did not s
On Wed, Dec 23, 2009 at 12:50 AM, Bruce Southey wrote:
> This still crashes Python 2.7 with the test_multiarray.TestIO.test_ascii.
Could you file a ticket next time ? I could not follow closely the
discussion the last week or so, and although I saw the crash, I missed
it was discussed already.
ti, 2009-12-22 kello 15:28 -0700, Charles R Harris kirjoitti: [clip]
> But what about the GIL? That's what I'm curious about. Do we need to
> hold the GIL to check and clear and error? If so, there are other
> places where this will matter. I was under the impression that each
> thread had it's own
On Tue, Dec 22, 2009 at 2:42 PM, Pauli Virtanen wrote:
> ti, 2009-12-22 kello 14:32 -0700, Charles R Harris kirjoitti:
> [clip]
> > Could you expand a bit on this? There are several places where
> > PyErr_Occurred are called and I am wondering if there is a problem. In
> > fact, I moved one such
ti, 2009-12-22 kello 14:32 -0700, Charles R Harris kirjoitti:
[clip]
> Could you expand a bit on this? There are several places where
> PyErr_Occurred are called and I am wondering if there is a problem. In
> fact, I moved one such check and a segfault went away, which made me
> suspicious...
I th
On Tue, Dec 22, 2009 at 12:40 PM, Pauli Virtanen wrote:
> ti, 2009-12-22 kello 10:16 -0700, Charles R Harris kirjoitti:
> [clip: PyOS_ascii_strtod -> PyOS_string_to_double]
> > The patch looks ok, but the functions handle errors differently and I
> > wonder if that has been completely audited.
>
ti, 2009-12-22 kello 10:16 -0700, Charles R Harris kirjoitti:
[clip: PyOS_ascii_strtod -> PyOS_string_to_double]
> The patch looks ok, but the functions handle errors differently and I
> wonder if that has been completely audited.
It can actually still crash from the same reason: PyOS_string_to_do
On Tue, Dec 22, 2009 at 8:50 AM, Bruce Southey wrote:
> On 12/22/2009 09:05 AM, David Cournapeau wrote:
>
>> Hi,
>>
>> I have just released the 2nd release candidate for numpy 1.4.0, which
>> fixes a few critical bugs founds since the RC1. Tarballs and binary
>> installers for numpy/scipy may be
On Tue, Dec 22, 2009 at 9:05 AM, David Cournapeau wrote:
> Hi,
>
> I have just released the 2nd release candidate for numpy 1.4.0, which
> fixes a few critical bugs founds since the RC1. Tarballs and binary
> installers for numpy/scipy may be found on
> https://sourceforge.net/projects/numpy.
>
>
On 12/22/2009 09:05 AM, David Cournapeau wrote:
Hi,
I have just released the 2nd release candidate for numpy 1.4.0, which
fixes a few critical bugs founds since the RC1. Tarballs and binary
installers for numpy/scipy may be found on
https://sourceforge.net/projects/numpy.
cheers,
David
___
Hi,
I have just released the 2nd release candidate for numpy 1.4.0, which
fixes a few critical bugs founds since the RC1. Tarballs and binary
installers for numpy/scipy may be found on
https://sourceforge.net/projects/numpy.
cheers,
David
___
NumPy-Dis
26 matches
Mail list logo
