Re: [Numpy-discussion] py3k execfile('setup.py')

On Tue, Aug 17, 2010 at 2:07 PM, Fernando Perez wrote: > On Sat, Aug 14, 2010 at 6:11 AM, Ralf Gommers > wrote: > > Installing into a local virtualenv (with either of the methods that work) > > looks good. Into /Library/Frameworks/..., nose refuses to run any tests, > due > > to the files being e

Re: [Numpy-discussion] py3k execfile('setup.py')

On Sat, Aug 14, 2010 at 6:11 AM, Ralf Gommers wrote: > Installing into a local virtualenv (with either of the methods that work) > looks good. Into /Library/Frameworks/..., nose refuses to run any tests, due > to the files being executable. But I think that's normal. Changing > permissions to 644

Re: [Numpy-discussion] py3k execfile('setup.py')

On Fri, Jul 30, 2010 at 12:04 AM, Pauli Virtanen wrote: > Thu, 29 Jul 2010 23:39:19 +0800, Ralf Gommers wrote: > > The execfile builtin has disappeared in python 3.x, so I'm trying to > > find another solution for the use of it in setupegg.py. So far I've > > tried > > I'd do something like this

Re: [Numpy-discussion] py3k execfile('setup.py')

Thu, 29 Jul 2010 23:39:19 +0800, Ralf Gommers wrote: > The execfile builtin has disappeared in python 3.x, so I'm trying to > find another solution for the use of it in setupegg.py. So far I've > tried I'd do something like this in "setup.py": ... + if os.environ.get('USE_SETUPTOOLS'): + i

[Numpy-discussion] py3k execfile('setup.py')

Hi, The execfile builtin has disappeared in python 3.x, so I'm trying to find another solution for the use of it in setupegg.py. So far I've tried if sys.version_info[0] >= 3: # 3.x doesn't have execfile anymore, so we define our own # The code below is syntactically valid 2.x, but 2.x th

Re: [Numpy-discussion] Py3k: making a py3k compat header available in installed numpy for scipy

2010/3/30 David Cournapeau > Pauli Virtanen wrote: [clip] > > At least, I don't see what I would like to change there. The only thing > > I wouldn't perhaps like to have in the long run are the PyString and > > possibly PyInt redefinition macros. > > I would also prefer a new name, instead of macr

Re: [Numpy-discussion] Py3k: making a py3k compat header available in installed numpy for scipy

Pauli Virtanen wrote: > ma, 2010-03-29 kello 19:13 +0900, David Cournapeau kirjoitti: >> I have worked on porting scipy to py3k, and it is mostly working. One >> thing which would be useful is to install something similar to >> npy_3kcompat.h in numpy, so that every scipy extension could share the

Re: [Numpy-discussion] Py3k: making a py3k compat header available in installed numpy for scipy

ma, 2010-03-29 kello 19:13 +0900, David Cournapeau kirjoitti: > I have worked on porting scipy to py3k, and it is mostly working. One > thing which would be useful is to install something similar to > npy_3kcompat.h in numpy, so that every scipy extension could share the > compat header. Is the cur

Re: [Numpy-discussion] Py3k: making a py3k compat header available in installed numpy for scipy

On Mon, Mar 29, 2010 at 4:13 AM, David Cournapeau wrote: > Hi, > > I have worked on porting scipy to py3k, and it is mostly working. One > thing which would be useful is to install something similar to > npy_3kcompat.h in numpy, so that every scipy extension could share the > compat header. Is the

[Numpy-discussion] Py3k: making a py3k compat header available in installed numpy for scipy

Hi, I have worked on porting scipy to py3k, and it is mostly working. One thing which would be useful is to install something similar to npy_3kcompat.h in numpy, so that every scipy extension could share the compat header. Is the current python 3 compatibility header usable "in the wild", or will

[Numpy-discussion] Py3k: including npy_config.h outside numpy.core

Hi, I have noticed that now some code outside numpy/core uses npy_config.h. As suggested by its location (numpy/core/src/private), it is specific to numpy/core, and should not be used outside. What's the rationale to use npy_config.h in numpy/core ? cheers, David ___

Re: [Numpy-discussion] Py3k and numpy

>From my experience working on my own projects and Cython: * the C code making Python C-API calls could be made to version-agnostic by using preprocessor macros, and even some compatibility header conditionally included. Perhaps the later would be the easiest for C-API calls (we have a lot already

Re: [Numpy-discussion] Py3k and numpy

On Fri, Dec 5, 2008 at 4:03 AM, Robert Kern <[EMAIL PROTECTED]> wrote: > On Thu, Dec 4, 2008 at 12:57, Charles R Harris > <[EMAIL PROTECTED]> wrote: >> >> >> On Thu, Dec 4, 2008 at 9:39 AM, Charles R Harris <[EMAIL PROTECTED]> >> wrote: >>> >>> >>> On Thu, Dec 4, 2008 at 1:20 AM, Erik Tollerud <[EM

Re: [Numpy-discussion] Py3k and numpy

On Thu, Dec 4, 2008 at 12:15 PM, Tommy Grav <[EMAIL PROTECTED]> wrote: > On Dec 4, 2008, at 2:03 PM, Robert Kern wrote: >> It does. What problems are people seeing? Is it just the Windows build >> that causes people to say "numpy doesn't work with Python 2.6"? > > There is currently no official Mac

Re: [Numpy-discussion] Py3k and numpy

On Dec 4, 2008, at 2:03 PM, Robert Kern wrote: > It does. What problems are people seeing? Is it just the Windows build > that causes people to say "numpy doesn't work with Python 2.6"? There is currently no official Mac OSX binary for numpy for python 2.6, but you can build it from source. Is the

Re: [Numpy-discussion] Py3k and numpy

On Thu, Dec 4, 2008 at 12:57, Charles R Harris <[EMAIL PROTECTED]> wrote: > > > On Thu, Dec 4, 2008 at 9:39 AM, Charles R Harris <[EMAIL PROTECTED]> > wrote: >> >> >> On Thu, Dec 4, 2008 at 1:20 AM, Erik Tollerud <[EMAIL PROTECTED]> >> wrote: >>> >>> I noticed that the Python 3000 final was release

Re: [Numpy-discussion] Py3k and numpy

On Thu, Dec 4, 2008 at 9:39 AM, Charles R Harris <[EMAIL PROTECTED]>wrote: > > > On Thu, Dec 4, 2008 at 1:20 AM, Erik Tollerud <[EMAIL PROTECTED]>wrote: > >> I noticed that the Python 3000 final was released today... is there >> any sense of how long it will take to get numpy working under 3k? I

Re: [Numpy-discussion] Py3k and numpy

On Thu, Dec 4, 2008 at 1:20 AM, Erik Tollerud <[EMAIL PROTECTED]>wrote: > I noticed that the Python 3000 final was released today... is there > any sense of how long it will take to get numpy working under 3k? I > would imagine it'll be a lot to adapt given the low-level change, but > is the work

[Numpy-discussion] Py3k and numpy

I noticed that the Python 3000 final was released today... is there any sense of how long it will take to get numpy working under 3k? I would imagine it'll be a lot to adapt given the low-level change, but is the work already in progress? ___ Numpy-discu

Re: [Numpy-discussion] Py3K

On Wed, Apr 16, 2008 at 2:56 PM, Stéfan van der Walt <[EMAIL PROTECTED]> wrote: > On 16/04/2008, Fernando Perez <[EMAIL PROTECTED]> wrote: > > On Tue, Apr 15, 2008 at 1:27 PM, Charles R Harris > > > > Oh, and making the transition will be made a lot easier by having a > > > complete > > > set o

Re: [Numpy-discussion] Py3K

Tim Michelsen wrote: >> This looks like something that need to go on a list for numpy 1.2. Can you >> > post a list of the specific problems that need to be addressed?Chuck > Maybe this post can give some hints: > All Things Pythonic > Python 3000 and You > by Guido van Rossum > March 17, 2008

Re: [Numpy-discussion] Py3K

On 16/04/2008, Fernando Perez <[EMAIL PROTECTED]> wrote: > On Tue, Apr 15, 2008 at 1:27 PM, Charles R Harris > > Oh, and making the transition will be made a lot easier by having a complete > > set of tests. Getting the tests and documentation into good state might be > > the best focus for our 1

Re: [Numpy-discussion] Py3K

> This looks like something that need to go on a list for numpy 1.2. Can you post a list of the specific problems that need to be addressed?Chuck Maybe this post can give some hints: All Things Pythonic Python 3000 and You by Guido van Rossum March 17, 2008 Summary I've posted the slides f

Re: [Numpy-discussion] Py3K

On Tue, Apr 15, 2008 at 1:27 PM, Charles R Harris <[EMAIL PROTECTED]> wrote: > Oh, and making the transition will be made a lot easier by having a complete > set of tests. Getting the tests and documentation into good state might be > the best focus for our 1.2 effort. +1 Bonus points for whoeve

Re: [Numpy-discussion] Py3K

On Tue, Apr 15, 2008 at 2:23 PM, Charles R Harris <[EMAIL PROTECTED]> wrote: > > > On Tue, Apr 15, 2008 at 1:21 PM, Bruce Southey <[EMAIL PROTECTED]> wrote: > > > Hi, > > You probably should start with the 2to3.py tool (see link at > > http://www.python.org/download/releases/3.0/). > > > > Looks l

Re: [Numpy-discussion] Py3K

On Tue, Apr 15, 2008 at 1:21 PM, Bruce Southey <[EMAIL PROTECTED]> wrote: > Hi, > You probably should start with the 2to3.py tool (see link at > http://www.python.org/download/releases/3.0/). > Looks like a lot of the changes aren't at all backward compatible. The new style print, for instance, d

Re: [Numpy-discussion] Py3K

Hi, You probably should start with the 2to3.py tool (see link at http://www.python.org/download/releases/3.0/). Bruce On Tue, Apr 15, 2008 at 2:16 PM, Jon Wright <[EMAIL PROTECTED]> wrote: > Charles R Harris wrote: > > > Jon Wright wrote: > > > > I tried to build numpy from svn using python

Re: [Numpy-discussion] Py3K

Charles R Harris wrote: > Jon Wright wrote: > > I tried to build numpy from svn using python-3.0a4 from python.org > and > noticed there are some issues (print, except syntax, distutils magic). > Has anyone been through this already? I actually want to start goi

Re: [Numpy-discussion] Py3K

On Tue, Apr 15, 2008 at 12:22 PM, Jon Wright <[EMAIL PROTECTED]> wrote: > I tried to build numpy from svn using python-3.0a4 from python.org and > noticed there are some issues (print, except syntax, distutils magic). > Has anyone been through this already? I actually want to start going > through

[Numpy-discussion] Py3K

I tried to build numpy from svn using python-3.0a4 from python.org and noticed there are some issues (print, except syntax, distutils magic). Has anyone been through this already? I actually want to start going through my own code, but I need numpy before I get started... Thanks, Jon