Jarrod Millman wrote:
>
> You can see them here:
> http://buildbot.scipy.org/builders/Linux_x86_64_Fedora/builds/486/steps/shell_2/logs/stdio
> http://buildbot.scipy.org/builders/Linux_x86_Fedora_Py2.6/builds/461/steps/shell_2/logs/stdio
>
> You have to search for them, because as Chuck pointed out
On Fri, May 23, 2008 at 11:16 PM, David Cournapeau
<[EMAIL PROTECTED]> wrote:
> Where do those errors appear ? I don't see them on the builbot. Are they
> 2.6 specific ? If yes, I would say ignore them, because 2.6 is not
> released yet, and is scheduled for september.
You can see them here:
http:
Jarrod Millman wrote:
>
> I would be happy to my only concern is that I would like to avoid
> releasing something that is broken. Can I safely ignore the 5
> buildbot failures that you pointed out yesterday?
>
Where do those errors appear ? I don't see them on the builbot. Are they
2.6 specif
On Thu, May 22, 2008 at 11:25 PM, Charles R Harris
<[EMAIL PROTECTED]> wrote:
> On Fri, May 23, 2008 at 12:10 AM, Charles R Harris
> <[EMAIL PROTECTED]> wrote:
>>
>> The python 2.6 buildbots are showing 5 failures that are being hidden by
>> valgrind.
>
> They seem to have fixed themselves, they w
On Fri, May 23, 2008 at 10:14 PM, Charles R Harris
<[EMAIL PROTECTED]> wrote:
> Will you just kick the d*mn thing out the door?
I would be happy to my only concern is that I would like to avoid
releasing something that is broken. Can I safely ignore the 5
buildbot failures that you pointed out ye
On Fri, May 23, 2008 at 3:31 PM, Jarrod Millman <[EMAIL PROTECTED]>
wrote:
> Hello,
>
> I plan to branch 1.1.x and tag 1.1.0 later today. As of now, please
> consider the trunk in an near absolute freeze. If you feel that there
> is some unimaginably important change that must take place before
gfortran is doing the trick. Must be a g95 misconfiguration or some other
thing that I have no ability to comprehend.
Thanks for the tip about the buggy numpy 1.04. That seemed to be the most
serious hurdle.
-Mark
On Fri, May 23, 2008 at 4:12 PM, Mark Miller <[EMAIL PROTECTED]>
wrote:
> It ap
It appears to be there: dllcrt2.o in g95\lib.
I'll re-install g95 to see if it helps. I'll also give gfortran in the
meantime too.
-Mark
On Fri, May 23, 2008 at 4:05 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Fri, May 23, 2008 at 5:59 PM, Mark Miller <[EMAIL PROTECTED]>
> wrote:
> > In t
On Fri, May 23, 2008 at 5:59 PM, Mark Miller <[EMAIL PROTECTED]> wrote:
> In this case, I am just using the Windows command prompt. I do not have a
> setup.cfg or pydistutils.cfg file. I did create a file in
> Python25\Lib\distutils called distutils.cfg containing 2 lines:
>
> [build]
> compiler
In this case, I am just using the Windows command prompt. I do not have a
setup.cfg or pydistutils.cfg file. I did create a file in
Python25\Lib\distutils called distutils.cfg containing 2 lines:
[build]
compiler = mingw32
That took care of the previous message. I am currently getting a 'faile
Ignore last message: I seem to have figured out the next environmental
variable that needed to be set. Still some lingering issues, but I'll work
on them some more before pestering here again.
thanks,
-Mark
On Fri, May 23, 2008 at 3:48 PM, Mark Miller <[EMAIL PROTECTED]>
wrote:
> Thank you...
On Fri, May 23, 2008 at 5:48 PM, Mark Miller <[EMAIL PROTECTED]> wrote:
> Thank you...getting much closer now.
>
> My current issue is this message:
>
> running build_ext
> error: don't know how to compile C/C++ code on platform 'nt' with 'g95'
> compiler.
>
> Any help?
What command line are you
Thank you...getting much closer now.
My current issue is this message:
running build_ext
error: don't know how to compile C/C++ code on platform 'nt' with 'g95'
compiler.
Any help?
Again, sorry to pester. I'm just pretty unfamiliar with these things. Once
I get environmental variables set up
On Fri, May 23, 2008 at 4:48 PM, Mark Miller <[EMAIL PROTECTED]> wrote:
> Super...I'll give it a try. Or should I just wait for the numpy 1.1
> release?
Probably. You can get a binary installer for the release candidate here:
http://www.ar.media.kyoto-u.ac.jp/members/david/archives/numpy-1.1.0rc
Super...I'll give it a try. Or should I just wait for the numpy 1.1
release?
thanks,
-Mark
On Fri, May 23, 2008 at 2:45 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Fri, May 23, 2008 at 4:00 PM, Mark Miller <[EMAIL PROTECTED]> wrote:
>
> > File "C:\Python25\lib\site-packages\numpy\f2py\ru
On Fri, May 23, 2008 at 4:00 PM, Mark Miller <[EMAIL PROTECTED]> wrote:
> File "C:\Python25\lib\site-packages\numpy\f2py\rules.py", line 1222, in
> buildmodule
> for l in '\n\n'.join(funcwrappers2)+'\n'.split('\n'):
> TypeError: cannot concatenate 'str' and 'list' objects
>
>
> Any thoughts?
To anyone who can help:
I recently got around to installing numpy 1.04 over an older version (numpy
1.04dev3982) on a Windows Vista machine. Since then, I have been unable to
compile some of my extensions using f2py. I also tested a fresh install of
numpy 1.04 on a new XP machine that has never
Hello,
I plan to branch 1.1.x and tag 1.1.0 later today. As of now, please
consider the trunk in an near absolute freeze. If you feel that there
is some unimaginably important change that must take place before we
branch and tag, please send an email to the mailing list including
your proposed p
To anyone who can help:
I recently got around to installing numpy 1.04 over an older version (numpy
1.04dev3982) on a Windows Vista machine. Since then, I have been unable to
compile some of my extensions using f2py. I also tested a fresh install of
numpy 1.04 on a new XP machine that has never
On Fri, May 23, 2008 at 11:44 AM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Fri, May 23, 2008 at 12:22 PM, Keith Goodman <[EMAIL PROTECTED]> wrote:
>
>> But the first example
>>
x = mp.matrix([[mp.nan]])
x
>> matrix([[ NaN]])
x.all()
>> True
x.any()
>> True
>>
>> is stil
On Fri, May 23, 2008 at 12:22 PM, Keith Goodman <[EMAIL PROTECTED]> wrote:
> But the first example
>
>>> x = mp.matrix([[mp.nan]])
>>> x
> matrix([[ NaN]])
>>> x.all()
> True
>>> x.any()
> True
>
> is still surprising.
On non-boolean arrays, .all() and .any() check each element to see if
it
On Fri, May 23, 2008 at 10:16 AM, Keith Goodman <[EMAIL PROTECTED]> wrote:
> I'm writing unit tests for a module that contains matrices. I was
> surprised that these are True:
>
>>> import numpy.matlib as mp
>>> x = mp.matrix([[mp.nan]])
>>> x.any()
> True
>>> x.all()
> True
>
> My use case is
I'm writing unit tests for a module that contains matrices. I was
surprised that these are True:
>> import numpy.matlib as mp
>> x = mp.matrix([[mp.nan]])
>> x.any()
True
>> x.all()
True
My use case is (x == y).all() where x and y are the same matrix except
that x contains one NaN. Certianl
Hi Peter & All,
On Fri, May 23, 2008 at 4:16 PM, Peter Creasey wrote:
> Hi Andrea,
>
> 2008/5/23 "Andrea Gavana" <[EMAIL PROTECTED]>:
>> And so on. The probelm with this approach is that I lose the original
>> indices for which I want all the inequality tests to succeed:
>
> To have the original
Hi Andrea,
2008/5/23 "Andrea Gavana" <[EMAIL PROTECTED]>:
> And so on. The probelm with this approach is that I lose the original
> indices for which I want all the inequality tests to succeed:
To have the original indices you just need to re-index your indices, as it were
idx = flatnonzero(xCe
On Fri, May 23, 2008 at 8:28 AM, Charles R Harris <[EMAIL PROTECTED]>
wrote:
> I've unsubscribed, resubscribed, changed addresses, and nothing works.
> Wassup with that?
>
Since the list works for Peter, I'm going to guess that something is
filtering the messages into limbo somewhere along the li
I've unsubscribed, resubscribed, changed addresses, and nothing works.
Wassup with that?
Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
Hi Stefan & All,
On Fri, May 23, 2008 at 1:02 AM, Stéfan van der Walt wrote:
> Hi Andrea
>
> 2008/5/23 Andrea Gavana <[EMAIL PROTECTED]>:
>> Thank you very much for this! I am going to try it and time it,
>> comparing it with the other implementations. I think I need to study a
>> bit your code as
28 matches
Mail list logo
