Hello all
A quick update: we're down to 16 active tickets, with 38 tickets
already closed for the 1.0.3 release. Thanks to all the bugfixers.
Summary of tickets for 1.0.3:
http://projects.scipy.org/scipy/numpy/milestone/1.0.3%20Release
Active tickets for 1.0.3:
http://projects.scipy.org/scipy
Hi,
in error logs as yours, always look for the first line which says "error". If
it is, like in your case, something like
On Sunday, 13. May 2007 19:21:15 dmitrey wrote:
> /usr/lib/gcc/x86_64-linux-gnu/4.1.2/include/limits.h:122:61: error:
> limits.h: No such file or directory
you are missing
Hi Dmitrey
On Sun, May 13, 2007 at 08:21:15PM +0300, dmitrey wrote:
> > Many people here are compiling numpy fine under Ubuntu. Do you have
> > write permissions to the output directory? What is the compiler error
> > given?
> >
> Sorry, I meant compiling Python2.5 and Octave, not numpy & Octa
Hi,
you have a problem with your Ubuntu installation, not with numpy.
Matthieu
2007/5/13, dmitrey <[EMAIL PROTECTED]>:
Stefan van der Walt wrote:
> On Sun, May 13, 2007 at 06:19:30PM +0300, dmitrey wrote:
>
>> Is it possible somehow to speedup numpy 1.0.3 appearing in Linux update
>> channels
Stefan van der Walt wrote:
> On Sun, May 13, 2007 at 06:19:30PM +0300, dmitrey wrote:
>
>> Is it possible somehow to speedup numpy 1.0.3 appearing in Linux update
>> channels? (as for me I'm interested in Ubuntu/Kubuntu, currently there
>> is v 1.0.1)
>> I tried to compile numpy 1.0.2, but, a
On Sun, May 13, 2007 at 06:19:30PM +0300, dmitrey wrote:
> Is it possible somehow to speedup numpy 1.0.3 appearing in Linux update
> channels? (as for me I'm interested in Ubuntu/Kubuntu, currently there
> is v 1.0.1)
> I tried to compile numpy 1.0.2, but, as well as in Octave compiling, it
> f
Is it possible somehow to speedup numpy 1.0.3 appearing in Linux update
channels? (as for me I'm interested in Ubuntu/Kubuntu, currently there
is v 1.0.1)
I tried to compile numpy 1.0.2, but, as well as in Octave compiling, it
failed because "c compiler can't create executable". gcc reinstallat
Hello all
On Sat, 12 May 2007, Charles R Harris wrote:
> On 5/12/07, Albert Strasheim <[EMAIL PROTECTED]> wrote:
> >
> >I've more or less finished my quick triage effort.
>
> Thanks, Albert. The tickets look much better organized now.
My pleasure. Stefan van der Walt has also gotten in on the a
On 5/12/07, Albert Strasheim <[EMAIL PROTECTED]> wrote:
I've more or less finished my quick triage effort.
Issues remaining to be resolved for the 1.0.3 release:
http://projects.scipy.org/scipy/numpy/query?status=new&status=assigned&status=reopened&milestone=1.0.3+Release
If they can't be fi
I've more or less finished my quick triage effort.
Issues remaining to be resolved for the 1.0.3 release:
http://projects.scipy.org/scipy/numpy/query?status=new&status=assigned&status=reopened&milestone=1.0.3+Release
If they can't be fixed for this release, we should move them over to
1.1 or may
Hello all
On Fri, 11 May 2007, David M. Cooke wrote:
> I've added a 1.0.3 milestone and set these to them (or to 1.1, according
> to Travis's comments).
I've reviewed some more tickets and filed everything that looks like it
can be resolved for this release under 1.0.3.
To see which tickets ar
On Fri, 11 May 2007, Travis Oliphant wrote:
> Thanks for the ticket reviews, Albert. That is really helpful.
My pleasure.
Found two more issues that look like they could be addressed:
http://projects.scipy.org/scipy/numpy/ticket/422
http://projects.scipy.org/scipy/numpy/ticket/450
Cheers,
A
On Sat, May 12, 2007 at 12:50:10AM +0200, Albert Strasheim wrote:
> Here's another issue with a patch that looks ready to go:
>
> http://projects.scipy.org/scipy/numpy/ticket/509
>
> Enhancement you might consider:
>
> http://projects.scipy.org/scipy/numpy/ticket/375
>
> And this one looks like
Albert Strasheim wrote:
> Here's another issue with a patch that looks ready to go:
>
> http://projects.scipy.org/scipy/numpy/ticket/509
>
> Enhancement you might consider:
>
> http://projects.scipy.org/scipy/numpy/ticket/375
>
> And this one looks like it can be closed:
>
> http://projects.scipy.o
Here's another issue with a patch that looks ready to go:
http://projects.scipy.org/scipy/numpy/ticket/509
Enhancement you might consider:
http://projects.scipy.org/scipy/numpy/ticket/375
And this one looks like it can be closed:
http://projects.scipy.org/scipy/numpy/ticket/395
Cheers,
Alber
Here are a few tickets that might warrant some attention from someone
who is intimately familiar with NumPy's internals ;-)
http://projects.scipy.org/scipy/numpy/ticket/390
http://projects.scipy.org/scipy/numpy/ticket/405
http://projects.scipy.org/scipy/numpy/ticket/466
http://projects.scipy.org/
Hi,
I am going to work on g3 f2py starting next week on full time
--- I am now hired by Simula Research Laboratory that will support
my work on f2py. I think I'll spend the next few months on g3 f2py.
However, this work should not affect the numpy release that you are
planning. I'll keep all major
Hi all,
I'd like to relase NumPy 1.0.3 next week (on Tuesday) along with a new
release of SciPy. Please let me know of changes that you are planning
on making before then.
Best,
-Travis
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
18 matches
Mail list logo
