ms that the _npy_ceil symbol is undefined. I looked at
> /build/src.macosx-10.6-intel-2.7/numpy/core/include/numpy/config.h and it
> contains:
>
> #define HAVE_CEIL
>
> Am I doing something wrong?
>
> regards,
>
> Andrew
>
> --
>
On Mon, Aug 6, 2012 at 8:31 PM, Robert Kern wrote:
> Those are not the original Fortran sources. The original Fortran sources are
> in the public domain as work done by a US federal employee.
>
> http://www.netlib.org/fftpack/
>
> Never trust the license of any code on John Burkardt's site. Track
On Thu, Jul 19, 2012 at 2:53 PM, Travis Oliphant wrote:
>
> On Jul 19, 2012, at 3:50 AM, Nathaniel Smith wrote:
>
>> So the underlying problem with the controversial inplace_increment
>> PR[1] is that currently, there's actually nothing in the public numpy
>> API that exposes the workings of numpy
I'm on 10.8 and am using the Apple Mac OS X Mountain Lion python (2.7.2).
Here's what I ended up doing, FWIW:
- I installed "pip" (sudu easy_install pip)
- I installed virtualenv
- created a new virtual environment [recommended since superpack installs a
bunch of development versions of the packag
On Tue, Aug 7, 2012 at 6:05 PM, Thiago Franco Moraes
wrote:
> A little off-topic, but related: Which python version do you recommend
> to install in Mac OS X 10.8? The native one? The one from python.org?
> or the one compiled via homebrew? And do you think it's better to use
> the 32 or 64 bits?
On Tue, Aug 7, 2012 at 5:35 PM, Chris Barker wrote:
> On Mon, Aug 6, 2012 at 8:51 PM, Tom Krauss
> wrote:
> > I got a new job, and a new mac book pro on which I just installed Mac OS
> X
> > 10.8.
>
> congrats -- on the job, and on an employer that gets you a mac!
>
> > I need to run SWIG to gen
A little off-topic, but related: Which python version do you recommend
to install in Mac OS X 10.8? The native one? The one from python.org?
or the one compiled via homebrew? And do you think it's better to use
the 32 or 64 bits?
Thanks!
On Tue, Aug 7, 2012 at 12:35 PM, Chris Barker wrote:
> On
On Tue, Aug 7, 2012 at 5:00 AM, Pierre GM wrote:
> It's generally considered a "very bad idea"(™) to install NumPy on a recent
> OSX system without specifying a destination. By default, the process will
> try to install on /Library/Frameworks/Python, overwriting the pre-installed
> version of Num
On Mon, Aug 6, 2012 at 8:51 PM, Tom Krauss wrote:
> I got a new job, and a new mac book pro on which I just installed Mac OS X
> 10.8.
congrats -- on the job, and on an employer that gets you a mac!
> I need to run SWIG to generate a shared object from C++ source that works
> with numpy.i. I'm
Here's a good article on the vagaries of python paths when installing a new
python. Thus you can check exactly how python finds its modules, to assure the
new install is working properly:
https://www.usenix.org/publications/login/august-2012-volume-37-number-4/import
John Mark Agosta
jmago...@
Andrew,
I'm afraid you did.
It's generally considered a "very bad idea"(™) to install NumPy on a recent
OSX system without specifying a destination. By default, the process will
try to install on /Library/Frameworks/Python, overwriting the pre-installed
version of NumPy that comes with your machi
On 6 August 2012 20:07, Alex Clark wrote:
> On 8/6/12 5:48 AM, Scott Sinclair wrote:
>> On 6 August 2012 11:04, Petro wrote:
>>> This is a general python question but I will ask it here. To
>>> install a new numpy on Debian testing I remove installed version with
>>> "aptitude purge python-numpy"
12 matches
Mail list logo
