Hi all,
I wanted to point out a couple of things about the new test framework
that you should keep in mind if you're writing tests:
- Don't use NumpyTestCase any more, just use TestCase (which is
available if you do from numpy.testing import *). Using NumpyTestCase
now causes a deprecation warni
On Tue, Jul 8, 2008 at 5:08 PM, Marek Wojciechowski
<[EMAIL PROTECTED]> wrote:
>
> cxx.linker_so = [cxx.linker_so[0], cxx.compiler_cxx[0]] + cxx.linker_so[2:]
>
> in line 303 of cccompiler.py in distutils.
>
Should be fixed in r5368. I will merge the change into 1.1.1 as well
cheers,
David
_
On Tue, Jul 8, 2008 at 3:30 PM, Anne Archibald
<[EMAIL PROTECTED]> wrote:
> In particular, the returned type is always "string of length four",
> which is very peculiar - why four? I realize that variable-length
> strings are a problem (object arrays, I guess?), as is returning
> arrays of varying
On Mon, Jul 7, 2008 at 3:11 PM, Chris Bartels <[EMAIL PROTECTED]> wrote:
> Hi David (and others)
>
> This issue is known:
> http://www.scipy.org/scipy/numpy/ticket/811
>
> I think this is an issue for the numpy developers. (I don't know how to fix
> this easily, i can try to install an older versio
On Tue, Jul 8, 2008 at 14:01, Keith Goodman <[EMAIL PROTECTED]> wrote:
> I don't know what to write for a doc string for alterdot and
> restoredot.
Then maybe you're the best one to figure it out. What details do you
think are missing from the current docstrings? What questions do they
leave you w
Hi,
I haven't checked out a recent numpy (( >>> N.__version__
'1.0.3.1'))
But could someone please check if the division has been changed from
'/' to '//' in these places:
C:\Priithon_25_win\numpy\core\numerictypes.py:142: DeprecationWarning:
classic int division
bytes = bits / 8
C:\Priithon_25_
Michael Abbott wrote:
> On Tue, 8 Jul 2008, Travis E. Oliphant wrote:
>
>> Michael Abbott wrote:
>>
>>> The attached patch fixes another reference count leak in the use of
>>> PyArray_DescrFromType.
>>>
>>>
>> The first part of this patch is good. The second is not needed.
>>
On Tue, Jul 8, 2008 at 3:23 PM, Michael Abbott <[EMAIL PROTECTED]>
wrote:
> On Tue, 8 Jul 2008, Travis E. Oliphant wrote:
> > Michael Abbott wrote:
> > > The attached patch fixes another reference count leak in the use of
> > > PyArray_DescrFromType.
> > >
> > The first part of this patch is good.
On Tue, Jul 8, 2008 at 16:23, Michael Abbott <[EMAIL PROTECTED]> wrote:
> On Tue, 8 Jul 2008, Travis E. Oliphant wrote:
>> Michael Abbott wrote:
>> > The attached patch fixes another reference count leak in the use of
>> > PyArray_DescrFromType.
>> >
>> The first part of this patch is good. The se
On Tue, 8 Jul 2008, Travis E. Oliphant wrote:
> Michael Abbott wrote:
> > The attached patch fixes another reference count leak in the use of
> > PyArray_DescrFromType.
> >
> The first part of this patch is good. The second is not needed.
I don't see that. The second part of the patch addr
On Tue, Jul 8, 2008 at 10:19 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 8, 2008 at 14:47, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>> On Tue, Jul 8, 2008 at 9:15 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
>>> On Tue, Jul 8, 2008 at 08:06, Ondrej Certik <[EMAIL PROTECTED]> wrote:
On Tue, Jul 8, 2008 at 14:47, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 8, 2008 at 9:15 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
>> On Tue, Jul 8, 2008 at 08:06, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>>> On Tue, Jul 8, 2008 at 11:48 AM, Tiziano Zito <[EMAIL PROTECTED]> wrote:
On Tue, Jul 8, 2008 at 9:15 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 8, 2008 at 08:06, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>> On Tue, Jul 8, 2008 at 11:48 AM, Tiziano Zito <[EMAIL PROTECTED]> wrote:
>>> Hi numpy-devs, I was the one reporting the original bug about missing ATLAS
On Tue, Jul 8, 2008 at 14:33, Frédéric Bastien <[EMAIL PROTECTED]> wrote:
> thanks for the information. What made my thought it was possible is
> that in the file site.cfg.example their is:
>
> # Given only this section, numpy.distutils will try to figure out which
> version
> # of FFTW you are us
thanks for the information. What made my thought it was possible is
that in the file site.cfg.example their is:
# Given only this section, numpy.distutils will try to figure out which version
# of FFTW you are using.
#[fftw]
#libraries = fftw3
Is this fftw section still usefull?
Frédéric Bastien
2008/7/8 Alan McIntyre <[EMAIL PROTECTED]>:
> On Tue, Jul 8, 2008 at 1:29 PM, Travis E. Oliphant
> <[EMAIL PROTECTED]> wrote:
>> Alan McIntyre wrote:
>>> 2. The behavior of __mul__ seems odd:
>>>
>> What is odd about this?
>>
>> It is patterned after
>>
>> >>> 'a' * 3
>> >>> 'a' * 4
>> >>> 'a' *
On Tue, Jul 8, 2008 at 14:14, Frédéric Bastien <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I want to compile numpy so that it use the optimized fftw librairy.
numpy itself does not support this. scipy does.
> In
> the site.cfg.example their is a section [fftw3] that I fill with:
>
> [fftw3]
> include_di
On Tue, Jul 8, 2008 at 08:06, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 8, 2008 at 11:48 AM, Tiziano Zito <[EMAIL PROTECTED]> wrote:
>> Hi numpy-devs, I was the one reporting the original bug about missing ATLAS
>> support in the debian lenny python-numpy package. AFAICT the source
>>
Hi,
I want to compile numpy so that it use the optimized fftw librairy. In
the site.cfg.example their is a section [fftw3] that I fill with:
[fftw3]
include_dirs = /usr/include
library_dirs = /usr/lib64
fftw3_libs = fftw3, fftw3f
fftw3_opt_libs = fftw3_threads, fftw3f_threads
when I
I don't know what to write for a doc string for alterdot and
restoredot. Any ideas?
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
On Tue, Jul 8, 2008 at 1:29 PM, Travis E. Oliphant
<[EMAIL PROTECTED]> wrote:
> Alan McIntyre wrote:
>> Since chararray doesn't currently have any tests, I'm writing some,
>> and I ran across a couple of things that didn't make sense to me:
>>
>> 1. The code for __mul__ is exactly the same as that
Hi Travis,
On Tue, Jul 8, 2008 at 11:26 AM, Travis E. Oliphant <[EMAIL PROTECTED]>
wrote:
> Michael Abbott wrote:
> > The attached patch fixes another reference count leak in the use of
> > PyArray_DescrFromType.
> >
> The first part of this patch is good. The second is not needed. Also,
> it
Alan McIntyre wrote:
> Since chararray doesn't currently have any tests, I'm writing some,
> and I ran across a couple of things that didn't make sense to me:
>
> 1. The code for __mul__ is exactly the same as that for __rmul__; is
> there any reason __rmul__ shouldn't just call __mul__?
>
Just
Michael Abbott wrote:
> The attached patch fixes another reference count leak in the use of
> PyArray_DescrFromType.
>
The first part of this patch is good. The second is not needed. Also,
it would be useful if you could write a test case that shows what is
leaking and how you determined t
On Tue, Jul 8, 2008 at 9:23 AM, Charles R Harris
<[EMAIL PROTECTED]> wrote:
> So what is the schedule? I have 4 bugs to fix and will get to them this
> weekend. Should we put together a bug action list?
Thanks for getting this conversation going. I have been meaning to
send an email for some time
On Tue, Jul 8, 2008 at 10:19 AM, Stéfan van der Walt <[EMAIL PROTECTED]>
wrote:
> 2008/7/8 Charles R Harris <[EMAIL PROTECTED]>:
> > I think we should try to get a quick bug fix version out by the end of
> the
> > month. What do others think?
>
> That was the plan. We wanted a release before the
2008/7/8 Stéfan van der Walt <[EMAIL PROTECTED]>:
> 2008/7/8 Charles R Harris <[EMAIL PROTECTED]>:
>> I think we should try to get a quick bug fix version out by the end of the
>> month. What do others think?
>
> That was the plan. We wanted a release before the conference -- early
> enough so tha
2008/7/8 Charles R Harris <[EMAIL PROTECTED]>:
> I think we should try to get a quick bug fix version out by the end of the
> month. What do others think?
That was the plan. We wanted a release before the conference -- early
enough so that Enthought could push out an EPD release. We'd also
like
I think we should try to get a quick bug fix version out by the end of the
month. What do others think?
Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
Dnia poniedziałek 07 lipiec 2008, [EMAIL PROTECTED] napisał:
> > > > File "/home/marek/tmp/numpy-1.1.0/numpy/distutils/ccompiler.py",
> > > > line 303, in CCompiler_cxx_compiler
> > > > + cxx.linker_so[2:]
> > > > TypeError: can only concatenate list (not "str") to list
> > >
> > > Just by re
On Tue, Jul 8, 2008 at 11:48 AM, Tiziano Zito <[EMAIL PROTECTED]> wrote:
> Hi numpy-devs, I was the one reporting the original bug about missing ATLAS
> support in the debian lenny python-numpy package. AFAICT the source
> python-numpy package in etch (numpy version 1.0.1) does not require
> atlas
On Tue, Jul 8, 2008 at 3:35 AM, Michael Abbott <[EMAIL PROTECTED]>
wrote:
> The attached patch fixes another reference count leak in the use of
> PyArray_DescrFromType.
>
> Could I ask that both this patch and my earlier one (ticket #843) be
> applied to subversion. Thank you.
>
I'll take a look
Hi numpy-devs, I was the one reporting the original bug about missing ATLAS
support in the debian lenny python-numpy package. AFAICT the source
python-numpy package in etch (numpy version 1.0.1) does not require
atlas to build
_dotblas.c, only lapack is needed. If you install the resulting binary
p
The attached patch fixes another reference count leak in the use of
PyArray_DescrFromType.
Could I ask that both this patch and my earlier one (ticket #843) be
applied to subversion. Thank you.
Definitely not enjoying this low level code.
commit 80e1aca1725dd4cd8e091126cf515c39ac3a33ff
Autho
Hi all,
Please review
http://codereview.appspot.com/2485
which adds `numpy.doc` as a way of documenting topics such as indexing
and broadcasting.
The corresponding trac ticket is
http://scipy.org/scipy/numpy/ticket/846
Regards
Stéfan
___
Numpy-discu
35 matches
Mail list logo
