Re: [Numpy-discussion] draft release guide

Francesc Alted wrote: > A Wednesday 24 March 2010 15:38:58 David Cournapeau escrigué: >> Oh, it is not that easy :) >> >> First, for some reason, the mingw-w64 project does not provide 64 >> hosted compilers, and since pushing for mingw cross compilation >> support in distutils would redefine the m

Re: [Numpy-discussion] draft release guide

What happens if you try to build a windows installer "python setup.py bdist_wininst" Also, have you attempted to specify the compiler in "$PYTHON_ROOT\Lib\distutils\distutils.cfg" ? I've got a script I use to manually change the "build" section of this file between [build] msvc and [build] min

[Numpy-discussion] Hiring: Software Developer, Scientific Applications

Enthought is hiring a Software Developer. See the description below, or on our website: http://www.enthought.com/company/sd-scientific-app.php Best, Amenity -- Amenity Applewhite Enthought, Inc. Scientific Computing Solutions www.enthought.com Software Developer The Software Developer at E

Re: [Numpy-discussion] What does float64 mean on a 32-bit machine?

reckoner wrote: > How can I have a float64 dtype on a 32-bit machine? For example: float64 is known as "double" in C, just for this reason. Modern FPUs use 64 bit (actually more bits), so you can get very good performance with float64 on 32 bit machines. And it is the standard Python float as w

Re: [Numpy-discussion] What does float64 mean on a 32-bit machine?

On Wed, Mar 24, 2010 at 17:38, reckoner wrote: > How can I have a float64 dtype on a 32-bit machine? For example: float64 is a 64-bit float on all machines. A "32-bit machine" refers only to the size of its memory address space and the size of the integer type used for pointers. It has no effect

[Numpy-discussion] What does float64 mean on a 32-bit machine?

How can I have a float64 dtype on a 32-bit machine? For example: In [90]: x = array([1/3],dtype=float32) In [91]: x Out[91]: array([ 0.3334], dtype=float32) In [92]: x = array([1/3],dtype=float64) In [93]: x Out[93]: array([ 0.]) Obviously, the float32 and float64 representations

Re: [Numpy-discussion] draft release guide

On Wed, Mar 24, 2010 at 3:31 PM, Francesc Alted wrote: > A Wednesday 24 March 2010 15:38:58 David Cournapeau escrigué: >> Oh, it is not that easy :) >> >> First, for some reason, the mingw-w64 project does not provide 64 >> hosted compilers, and since pushing for mingw cross compilation >> support

Re: [Numpy-discussion] draft release guide

A Wednesday 24 March 2010 15:38:58 David Cournapeau escrigué: > Oh, it is not that easy :) > > First, for some reason, the mingw-w64 project does not provide 64 > hosted compilers, and since pushing for mingw cross compilation > support in distutils would redefine the meaning of insanity, I build

[Numpy-discussion] numpy.array(arr.flat) mutates arr if arr.flags.fortran: bug?

Hello, I assume it is a bug that calling numpy.array() on a flatiter of a fortran-strided array that owns its own data causes that array to be rearranged somehow? Not sure what happens with a fancier-strided array that also owns its own data (because I'm not sure how to create one of those

Re: [Numpy-discussion] StringIO test failure with Python3.1.2

Wed, 24 Mar 2010 13:35:51 -0500, Bruce Southey wrote: [clip] > elif isinstance(item, collections.Callable): >File "/usr/local/lib/python3.1/abc.py", line 121, in >__instancecheck__ > subclass = instance.__class__ > AttributeError: 'PyCapsule' object has no attribute '__class__' S

Re: [Numpy-discussion] StringIO test failure with Python3.1.2

On 03/24/2010 01:25 PM, Charles R Harris wrote: On Wed, Mar 24, 2010 at 8:17 AM, Bruce Southey > wrote: Hi, Wow, this is really impressive! I installed the svn numpy version '2.0.0.dev8300' with the latest Python 3.1.2 and it works! All the

Re: [Numpy-discussion] StringIO test failure with Python3.1.2

On Wed, Mar 24, 2010 at 8:17 AM, Bruce Southey wrote: > Hi, > Wow, this is really impressive! > I installed the svn numpy version '2.0.0.dev8300' with the latest Python > 3.1.2 and it works! > > All the tests pass except: > test_utils.test_lookfor > > I am guessing that it is this line as the oth

Re: [Numpy-discussion] draft release guide

Francesc Alted wrote: > Also, I have read the draft and I cannot see references to 64-bit binary > packages. With the advent of Windows 7 and Mac OSX Snow Leopard, 64-bit are > way more spread than before, so they would be a great thing to deliver, IMO. True, however the situation is a bit ugly

Re: [Numpy-discussion] StringIO test failure with Python3.1.2

On Wed, Mar 24, 2010 at 9:59 AM, Charles R Harris wrote: > > > On Wed, Mar 24, 2010 at 9:29 AM, Pauli Virtanen wrote: > >> ke, 2010-03-24 kello 09:20 -0600, Charles R Harris kirjoitti: >> > What would be the best fix? Should we rename io to something like >> > npyio? >> >> That, or: >> >> Disabl

Re: [Numpy-discussion] StringIO test failure with Python3.1.2

On 03/24/2010 10:30 AM, Pauli Virtanen wrote: > ke, 2010-03-24 kello 10:28 -0500, Robert Kern kirjoitti: > >> utils.py is the only file in there that imports StringIO. It should >> probably do a local import "from io import BytesIO" because io.py >> already contains some Python3-awareness: >> >

Re: [Numpy-discussion] StringIO test failure with Python3.1.2

On Wed, Mar 24, 2010 at 9:29 AM, Pauli Virtanen wrote: > ke, 2010-03-24 kello 09:20 -0600, Charles R Harris kirjoitti: > > What would be the best fix? Should we rename io to something like > > npyio? > > That, or: > > Disable import conversions in tools/py3tool.py for that particular file, > and

Re: [Numpy-discussion] StringIO test failure with Python3.1.2

ke, 2010-03-24 kello 10:28 -0500, Robert Kern kirjoitti: > utils.py is the only file in there that imports StringIO. It should > probably do a local import "from io import BytesIO" because io.py > already contains some Python3-awareness: > > if sys.version_info[0] >= 3: > import io > Bytes

Re: [Numpy-discussion] StringIO test failure with Python3.1.2

ke, 2010-03-24 kello 09:20 -0600, Charles R Harris kirjoitti: > What would be the best fix? Should we rename io to something like > npyio? That, or: Disable import conversions in tools/py3tool.py for that particular file, and fix any import errors manually so that the same code works both for Pyt

Re: [Numpy-discussion] StringIO test failure with Python3.1.2

On Wed, Mar 24, 2010 at 10:20, Charles R Harris wrote: > > On Wed, Mar 24, 2010 at 9:07 AM, Robert Kern wrote: >> >> On Wed, Mar 24, 2010 at 09:43, David Cournapeau >> wrote: >> > On Wed, Mar 24, 2010 at 11:35 PM, Nadav Horesh >> > wrote: >> >> Any idea why >> >> >> >>  from .io import StringIO

Re: [Numpy-discussion] StringIO test failure with Python3.1.2

On Wed, Mar 24, 2010 at 9:07 AM, Robert Kern wrote: > On Wed, Mar 24, 2010 at 09:43, David Cournapeau > wrote: > > On Wed, Mar 24, 2010 at 11:35 PM, Nadav Horesh > wrote: > >> Any idea why > >> > >> from .io import StringIO > >> > >> and not > >> > >> from io import StringIO > >> > >> ??? > >

Re: [Numpy-discussion] StringIO test failure with Python3.1.2

On Wed, Mar 24, 2010 at 09:43, David Cournapeau wrote: > On Wed, Mar 24, 2010 at 11:35 PM, Nadav Horesh wrote: >> Any idea why >> >>  from .io import StringIO >> >> and not >> >>  from io import StringIO >> >> ??? >> >> (Why is the extra "." before "io") > > Maybe a bug in py2to3, because StringI

Re: [Numpy-discussion] StringIO test failure with Python3.1.2

On Wed, Mar 24, 2010 at 09:35, Nadav Horesh wrote: > Any idea why > >  from .io import StringIO > > and not > >  from io import StringIO > > ??? > > (Why is the extra "." before "io") It is a relative import, i.e. numpy.lib.io . -- Robert Kern "I have come to believe that the whole world is an

Re: [Numpy-discussion] StringIO test failure with Python3.1.2

On Wed, Mar 24, 2010 at 09:43, David Cournapeau wrote: > On Wed, Mar 24, 2010 at 11:35 PM, Nadav Horesh wrote: >> Any idea why >> >>  from .io import StringIO >> >> and not >> >>  from io import StringIO >> >> ??? >> >> (Why is the extra "." before "io") > > Maybe a bug in py2to3, because StringI

Re: [Numpy-discussion] StringIO test failure with Python3.1.2

On Wed, Mar 24, 2010 at 11:35 PM, Nadav Horesh wrote: > Any idea why > >  from .io import StringIO > > and not > >  from io import StringIO > > ??? > > (Why is the extra "." before "io") Maybe a bug in py2to3, because StringIO is in io in python 3, and we have a io module in numpy (.io is the new

Re: [Numpy-discussion] StringIO test failure with Python3.1.2

Any idea why from .io import StringIO and not from io import StringIO ??? (Why is the extra "." before "io") Nadav -Original Message- From: numpy-discussion-boun...@scipy.org on behalf of Bruce Southey Sent: Wed 24-Mar-10 16:17 To: Discussion of Numerical Python Subject: [Nump

Re: [Numpy-discussion] draft release guide

On Wed, Mar 24, 2010 at 11:25 PM, Francesc Alted wrote: > > Ok.  I've been having a try at mingw-w64 project: > > http://mingw-w64.sourceforge.net/ > > with no success so far with build numpy: > > $ python setup.py build --compiler=mingw32 Oh, it is not that easy :) First, for some reason, the

Re: [Numpy-discussion] draft release guide

A Wednesday 24 March 2010 12:00:36 David Cournapeau escrigué: > On Wed, Mar 24, 2010 at 6:50 PM, Francesc Alted wrote: > > Also, I have read the draft and I cannot see references to 64-bit binary > > packages. With the advent of Windows 7 and Mac OSX Snow Leopard, 64-bit > > are way more spread t

[Numpy-discussion] StringIO test failure with Python3.1.2

Hi, Wow, this is really impressive! I installed the svn numpy version '2.0.0.dev8300' with the latest Python 3.1.2 and it works! All the tests pass except: test_utils.test_lookfor I am guessing that it is this line as the other io imports do not have the period. from .io import StringIO ==

Re: [Numpy-discussion] draft release guide

On Wed, Mar 24, 2010 at 6:50 PM, Francesc Alted wrote: > Also, I have read the draft and I cannot see references to 64-bit binary > packages.  With the advent of Windows 7 and Mac OSX Snow Leopard, 64-bit are > way more spread than before, so they would be a great thing to deliver, IMO. For Mac

Re: [Numpy-discussion] draft release guide

On Wed, Mar 24, 2010 at 5:50 PM, Francesc Alted wrote: > A Wednesday 24 March 2010 01:49:50 Ralf Gommers escrigué: > > On Wed, Mar 24, 2010 at 1:40 AM, Christopher Barker > > > > wrote: > > > Ralf Gommers wrote: > > > > At http://github.com/rgommers/NumPy-release-guide you can find a > > > > summ

Re: [Numpy-discussion] draft release guide

A Wednesday 24 March 2010 01:49:50 Ralf Gommers escrigué: > On Wed, Mar 24, 2010 at 1:40 AM, Christopher Barker > > wrote: > > Ralf Gommers wrote: > > > At http://github.com/rgommers/NumPy-release-guide you can find a > > > summary of how to set up your system to build numpy binaries on OS X. I >