Hi,
Do you plan to make some noise about that when numpy2.0 will be release?
IMHO you should.
Do you for instance plan to have a clear announcement on the scipy web site?
Xavier
> Hi,
>
> The test suite passes now on Pythons 2.4 - 3.1. Further testing is very
> welcome -- also on Python 2.x. Plea
su, 2010-02-21 kello 20:45 +0100, Dag Sverre Seljebotn kirjoitti:
> Pauli Virtanen wrote:
[clip]
> > Currently, Scipy has some known failures because of
> >
> > (i) removed new= keyword in numpy.histogram
> > (ii) Cython supports only native size/alignment PEP 3118 buffers, and
> > Numpy array
Pauli Virtanen wrote:
> Hi,
>
> The test suite passes now on Pythons 2.4 - 3.1. Further testing is very
> welcome -- also on Python 2.x. Please check that your favourite software
> still builds and works with SVN trunk Numpy.
>
> Currently, Scipy has some known failures because of
>
> (i) removed n
AWESOME :)
On Sun, Feb 21, 2010 at 1:43 PM, Pauli Virtanen wrote:
> Hi,
>
> The test suite passes now on Pythons 2.4 - 3.1. Further testing is very
> welcome -- also on Python 2.x. Please check that your favourite software
> still builds and works with SVN trunk Numpy.
>
> Currently, Scipy has s
Hi,
The test suite passes now on Pythons 2.4 - 3.1. Further testing is very
welcome -- also on Python 2.x. Please check that your favourite software
still builds and works with SVN trunk Numpy.
Currently, Scipy has some known failures because of
(i) removed new= keyword in numpy.histogram
(ii) C
ti, 2010-02-16 kello 12:11 -0600, Bruce Southey kirjoitti:
[clip]
> I managed to get 2to3 (I think from Python 3.1) to crash and isolated
> it to the file numpy-work/numpy/lib/arrayterator.py
>
> So I might hitting this ' assertion error in 2to3' bug:
> http://bugs.python.org/issue7824
>
> I try
New try new error:
gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
build/temp.linux-x86_64-3.1/numpy/core/src/multiarray/multiarraymodule_onefile.o
-Lbuild/temp.linux-x86_64-3.1 -lnpymath -lm -o
build/lib.linux-x86_64-3.1/numpy/core/multiarray.so
/usr/bin/ld:
build/temp.linux-x86_64-3.1/numpy
On 02/15/2010 10:55 AM, Pauli Virtanen wrote:
ma, 2010-02-15 kello 10:18 -0600, Bruce Southey kirjoitti:
[clip]
Is there a correct way to get Python3.1 to find the relative path on Linux?
I can change the import statement to work but I do not think that is viable.
You need to use rela
ma, 2010-02-15 kello 15:51 -0700, Charles R Harris kirjoitti:
[clip]
> A lot of the remaining failures are of this sort:
>
> x: array([b'pi', b'pi', b'pi', b'four', b'five'],
> dtype='|S8')
> y: array(['pi', 'pi', 'pi', 'four', 'five'],
> dtype='
>
> This looks fixable by specify
On Mon, Feb 15, 2010 at 3:19 PM, Charles R Harris wrote:
>
>
> On Mon, Feb 15, 2010 at 3:05 PM, Pauli Virtanen wrote:
>
>> ma, 2010-02-15 kello 21:58 +0200, Pauli Virtanen kirjoitti:
>> [clip]
>> > > Program received signal SIGABRT, Aborted.
>> > > 0x7fff84e1efe6 in __kill ()
>> > > (gdb) bt
On Mon, Feb 15, 2010 at 3:05 PM, Pauli Virtanen wrote:
> ma, 2010-02-15 kello 21:58 +0200, Pauli Virtanen kirjoitti:
> [clip]
> > > Program received signal SIGABRT, Aborted.
> > > 0x7fff84e1efe6 in __kill ()
> > > (gdb) bt
> > > #0 0x7fff84e1efe6 in __kill ()
> > > #1 0x7fff84ebfe32
ma, 2010-02-15 kello 21:58 +0200, Pauli Virtanen kirjoitti:
[clip]
> > Program received signal SIGABRT, Aborted.
> > 0x7fff84e1efe6 in __kill ()
> > (gdb) bt
> > #0 0x7fff84e1efe6 in __kill ()
> > #1 0x7fff84ebfe32 in abort ()
> > #2 0x0001000cd715 in Py_FatalError ()
> > #3 0x0
On 15 February 2010 23:11, Charles R Harris wrote:
>> OSX, 64-bit with (I'm assuming) UCS2 (since I didn't specify the UCS4
>> variant when building). Is there an easy way to check the unicode
>> width?
>>
> I found it in the pyconfig.h file:
>
> pyconfig.h:#define Py_UNICODE_SIZE 4'
Aha!
#defi
2010/2/15 Stéfan van der Walt
> On 15 February 2010 21:58, Pauli Virtanen wrote:
> > ma, 2010-02-15 kello 21:41 +0200, Stéfan van der Walt kirjoitti:
> > [clip]
> >> .Fatal Python error: Inconsistent interned string
> >> state.
> >>
> > The platform is OSX -- 32 or 64 bits? Is yo
On 15 February 2010 21:58, Pauli Virtanen wrote:
> ma, 2010-02-15 kello 21:41 +0200, Stéfan van der Walt kirjoitti:
> [clip]
>> .Fatal Python error: Inconsistent interned string
>> state.
>>
> The platform is OSX -- 32 or 64 bits? Is your Python unicode narrow or
> wide? Which test
On Mon, Feb 15, 2010 at 12:58 PM, Pauli Virtanen wrote:
> ma, 2010-02-15 kello 21:41 +0200, Stéfan van der Walt kirjoitti:
> [clip]
> > > On Python 3.1, the numpymemoryview_init is a stub function that does
> > > nothing. I guess this is another single-file compilation issue -- the
> > > new file
ma, 2010-02-15 kello 21:41 +0200, Stéfan van der Walt kirjoitti:
[clip]
> > On Python 3.1, the numpymemoryview_init is a stub function that does
> > nothing. I guess this is another single-file compilation issue -- the
> > new file should be included in multiarraymodule_onefile.c. Should be
> > fix
2010/2/15 Stéfan van der Walt :
> Thanks, it works now.
Progress: the unit test suite starts to run, but fails soon after.
.Fatal Python error: Inconsistent interned string state.
Program received signal SIGABRT, Aborted.
0x7fff84e1efe6 in __kill ()
(gdb) bt
#0 0x7fff84
On 15 February 2010 21:19, Pauli Virtanen wrote:
> Oh crap, nothing seems to work for anyone else ;)
Don't speak too soon: we have import!
> On Python 3.1, the numpymemoryview_init is a stub function that does
> nothing. I guess this is another single-file compilation issue -- the
> new file sho
ma, 2010-02-15 kello 21:07 +0200, Stéfan van der Walt kirjoitti:
[clip]
> After your latest changes, numpy builds on OSX, although importing is
> still broken:
>
> from . import multiarray
> ImportError:
> dlopen(/Users/stefan/lib/python3.1/site-packages/numpy/core/multiarray.so,
> 2): Symbol
Hi Pauli
Well done! You and Charles have made huge strides since last I looked
at the problem.
After your latest changes, numpy builds on OSX, although importing is
still broken:
from . import multiarray
ImportError:
dlopen(/Users/stefan/lib/python3.1/site-packages/numpy/core/multiarray.so
On Mon, Feb 15, 2010 at 10:55 AM, Pauli Virtanen wrote:
> ma, 2010-02-15 kello 10:18 -0600, Bruce Southey kirjoitti:
> [clip]
>> Is there a correct way to get Python3.1 to find the relative path on Linux?
>> I can change the import statement to work but I do not think that is viable.
>
> You need
On Mon, Feb 15, 2010 at 10:55 AM, Pauli Virtanen wrote:
> ma, 2010-02-15 kello 10:23 -0700, Charles R Harris kirjoitti:
> [clip]
> > Segfaults:
> >
> > test_multiarray.TestNewBufferProtocol.test_export_simple_1d ... FAIL
> > test_multiarray.TestNewBufferProtocol.test_export_simple_nd ... ok
> > t
ma, 2010-02-15 kello 10:23 -0700, Charles R Harris kirjoitti:
[clip]
> Segfaults:
>
> test_multiarray.TestNewBufferProtocol.test_export_simple_1d ... FAIL
> test_multiarray.TestNewBufferProtocol.test_export_simple_nd ... ok
> test_multiarray.TestNewBufferProtocol.test_export_subarray ... FAIL
> tes
On Mon, Feb 15, 2010 at 9:55 AM, Pauli Virtanen wrote:
> ma, 2010-02-15 kello 10:18 -0600, Bruce Southey kirjoitti:
> [clip]
> > Is there a correct way to get Python3.1 to find the relative path on
> Linux?
> > I can change the import statement to work but I do not think that is
> viable.
>
> You
ma, 2010-02-15 kello 10:18 -0600, Bruce Southey kirjoitti:
[clip]
> Is there a correct way to get Python3.1 to find the relative path on Linux?
> I can change the import statement to work but I do not think that is viable.
You need to use relative imports. 2to3 should be able to take care of
this.
On 02/15/2010 12:55 AM, Pauli Virtanen wrote:
> ma, 2010-02-15 kello 00:38 +0100, Xavier Gnata kirjoitti:
>
>> Ok!
>> git clone git://github.com/pv/numpy-work.git
>> git checkout origin/py3k
>> NPY_SEPARATE_BUILD=1 python3.1 setup.py build
>>
>> but now it fails during the build:
>>
>> In file
ma, 2010-02-15 kello 00:38 +0100, Xavier Gnata kirjoitti:
> Ok!
> git clone git://github.com/pv/numpy-work.git
> git checkout origin/py3k
> NPY_SEPARATE_BUILD=1 python3.1 setup.py build
>
> but now it fails during the build:
>
> In file included from numpy/core/src/multiarray/buffer.c:14,
> from
28 matches
Mail list logo
