Charles R Harris wrote:
>
> Ah... Is this going to be a problem with Debian installs?
No, I meant that Lenny has a clear rule for transition, whereas I could
not find such information for Ubuntu. Since the transition happened
during the Hardy developement time-frame, I don't know what Ubuntu did
On Tue, May 20, 2008 at 8:32 PM, David Cournapeau <
[EMAIL PROTECTED]> wrote:
> Charles R Harris wrote:
> > Curious bug on Stefan's Ubuntu build client:
> >
> > ImportError: /usr/lib/atlas/libblas.so.3gf: undefined symbol:
> _gfortran_st_write_done
> > make[1]: *** [test] Error 1
>
> Unfortunately
Charles R Harris wrote:
> Curious bug on Stefan's Ubuntu build client:
>
> ImportError: /usr/lib/atlas/libblas.so.3gf: undefined symbol:
> _gfortran_st_write_done
> make[1]: *** [test] Error 1
Unfortunately not curious and very well known: I bet the client is
configured to build with g77; libbla
Charles R Harris wrote:
Hi Chuck,
> Curious bug on Stefan's Ubuntu build client:
>
> ImportError: /usr/lib/atlas/libblas.so.3gf: undefined symbol:
> _gfortran_st_write_done
> make[1]: *** [test] Error 1
> Anyone know what that is about?
>
You need to link -lgfortran since the blas you use was com
Curious bug on Stefan's Ubuntu build client:
ImportError: /usr/lib/atlas/libblas.so.3gf: undefined symbol:
_gfortran_st_write_done
make[1]: *** [test] Error 1
Anyone know what that is about?
Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scip
On Tue, May 20, 2008 at 2:26 PM, Charles R Harris
<[EMAIL PROTECTED]> wrote:
> How about ticket 770? Did Roberts endianess fixes cover that?
Yes.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interpret
On Tue, May 20, 2008 at 1:16 PM, Jarrod Millman <[EMAIL PROTECTED]>
wrote:
> On Tue, May 20, 2008 at 12:10 PM, Charles R Harris
> <[EMAIL PROTECTED]> wrote:
> > Can we close ticket 605, Incorrect Behavior of Numpy Histogram?
> > http://projects.scipy.org/scipy/numpy/ticket/605
>
> Yes, but we need
On Tue, May 20, 2008 at 12:10 PM, Charles R Harris
<[EMAIL PROTECTED]> wrote:
> Can we close ticket 605, Incorrect Behavior of Numpy Histogram?
> http://projects.scipy.org/scipy/numpy/ticket/605
Yes, but we need to create a new ticket for 1.2 detailing the planned
changes. If no one else gets to
Can we close ticket 605, Incorrect Behavior of Numpy Histogram?
http://projects.scipy.org/scipy/numpy/ticket/605
Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
Charles R Harris wrote:
> Absolutely! If anybody has access to such a machine and is willing to
> let a build-slave run on it, please let me know and I'll send you the
> necessary configuration files.
>
> The current Mac machine seems to have a configuration problem.
I've got a PPC M
2008/5/20 Charles R Harris <[EMAIL PROTECTED]>:
> The current Mac machine seems to have a configuration problem. If anyone out
> there has an SGI machine we could use that too. I heart the buildbot.
I mailed Barry, he'll reset it for us. I'm glad the buildbot makes
you happy, Charles :)
Regards
On Tue, May 20, 2008 at 10:30 AM, Stéfan van der Walt <[EMAIL PROTECTED]>
wrote:
> 2008/5/20 Charles R Harris <[EMAIL PROTECTED]>:
> >
> >
> > On Tue, May 20, 2008 at 9:48 AM, Jarrod Millman <[EMAIL PROTECTED]>
> > wrote:
> >>
> >> On Tue, May 20, 2008 at 8:37 AM, Charles R Harris
> >> <[EMAIL PRO
Stéfan van der Walt wrote:
> 2008/5/20 Charles R Harris <[EMAIL PROTECTED]>:
>
>> On Tue, May 20, 2008 at 9:48 AM, Jarrod Millman <[EMAIL PROTECTED]>
>> wrote:
>>
>>> On Tue, May 20, 2008 at 8:37 AM, Charles R Harris
>>> <[EMAIL PROTECTED]> wrote:
>>>
Two of the buildbots are sh
2008/5/20 Charles R Harris <[EMAIL PROTECTED]>:
>
>
> On Tue, May 20, 2008 at 9:48 AM, Jarrod Millman <[EMAIL PROTECTED]>
> wrote:
>>
>> On Tue, May 20, 2008 at 8:37 AM, Charles R Harris
>> <[EMAIL PROTECTED]> wrote:
>> > Two of the buildbots are showing problems, probably installation
>> > related
2008/5/20 Charles R Harris <[EMAIL PROTECTED]>:
> Two of the buildbots are showing problems, probably installation related,
> but it would be nice to see all green before the release.
Thanks, fixed in SVN.
Regards
Stéfan
___
Numpy-discussion mailing lis
On Tue, May 20, 2008 at 9:48 AM, Jarrod Millman <[EMAIL PROTECTED]>
wrote:
> On Tue, May 20, 2008 at 8:37 AM, Charles R Harris
> <[EMAIL PROTECTED]> wrote:
> > Two of the buildbots are showing problems, probably installation related,
> > but it would be nice to see all green before the release.
>
On Tue, May 20, 2008 at 8:37 AM, Charles R Harris
<[EMAIL PROTECTED]> wrote:
> Two of the buildbots are showing problems, probably installation related,
> but it would be nice to see all green before the release.
Absolutely. Thanks for catching this.
--
Jarrod Millman
Computational Infrastructu
On Tue, May 20, 2008 at 6:11 AM, Jarrod Millman <[EMAIL PROTECTED]>
wrote:
> On Tue, May 20, 2008 at 3:47 AM, Pearu Peterson <[EMAIL PROTECTED]> wrote:
> > On Tue, May 20, 2008 12:59 pm, Jarrod Millman wrote:
> >
> >> Commits to the trunk (1.2.x) should follow these rules:
> >>
> >> 1. Documentat
On Tue, May 20, 2008 at 3:47 AM, Pearu Peterson <[EMAIL PROTECTED]> wrote:
> On Tue, May 20, 2008 12:59 pm, Jarrod Millman wrote:
>
>> Commits to the trunk (1.2.x) should follow these rules:
>>
>> 1. Documentation fixes are allowed and strongly encouraged.
>> 2. Bug-fixes are strongly encouraged.
2008/5/20 Pearu Peterson <[EMAIL PROTECTED]>:
>> 7. If you fix a bug, it must have tests.
>
> Since you asked, I have a problem with the rule 7 when applying
> it to packages like numpy.distutils and numpy.f2py, for instance.
>
> Do you realize that there exists bugs/features for which unittests c
Pearu Peterson wrote:
>
> Since you asked, I have a problem with the rule 7 when applying
> it to packages like numpy.distutils and numpy.f2py, for instance.
>
Although Jarrod did not mention it, I think everybody agrees that
distutils is not really testable, by its nature and design. But that
On Tue, May 20, 2008 12:59 pm, Jarrod Millman wrote:
> Commits to the trunk (1.2.x) should follow these rules:
>
> 1. Documentation fixes are allowed and strongly encouraged.
> 2. Bug-fixes are strongly encouraged.
> 3. Do not break backwards compatibility.
> 4. New features are permissible.
>
2008/5/20 Jarrod Millman <[EMAIL PROTECTED]>:
> In response to some of the recent discussion (and confusion)
> surrounding my plan for the trunk and 1.2 development over the next
> month or two, I propose the following:
Thank you for the clarification, Jarrod. Your plan is sound, I'm on board.
R
Hello everyone,
In response to some of the recent discussion (and confusion)
surrounding my plan for the trunk and 1.2 development over the next
month or two, I propose the following:
1. Stay with the "original" plan until Thursday, May 22nd. That is,
all commits to the trunk should be extremel
24 matches
Mail list logo
