Robert Kern wrote:
>> Program received signal SIGTRAP, Trace/breakpoint trap.
>>
>> which I cannot parse. Any ideas?
>
> Possibly you are linking against the wrong wx libraries.
It's worth a try, but that doesn't look familiar.
New MPL binaries have been put up on pythonmac.org/packages.
I'm
On 1/13/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> > Import of pylab still fails. The failure is now different. Using gdb I get
> > --snip--
> > Reading symbols for shared libraries . done
> > Reading symbols for shared libraries .. done
> > 20:48:11: Debug: ../src/common/object.cpp(224): asser
Erin Sheldon wrote:
> On 1/13/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> --snip--
>> Now, since the bug is actually in freetype, not matplotlib or numpy, I
>> suggest
>> finding a new build of freetype. I use MacPorts and have had absolutely no
>> trouble with it.
>
>
> I switched to using mac
On 1/13/07, Robert Kern <[EMAIL PROTECTED]> wrote:
--snip--
>
> Now, since the bug is actually in freetype, not matplotlib or numpy, I suggest
> finding a new build of freetype. I use MacPorts and have had absolutely no
> trouble with it.
I switched to using macports, and included your modificati
Erin Sheldon wrote:
> On 1/9/07, Robert Kern <[EMAIL PROTECTED]> wrote:
>> Erin Sheldon wrote:
>>> I'm finally getting to this, I'm on the road. Here is
>>> what gdb gives me
>>>
>>> --snip--
>>> Reading symbols for shared libraries . done
>>> Reading symbols for shared libraries . done
>>> Readin
On 1/9/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> Erin Sheldon wrote:
> > I'm finally getting to this, I'm on the road. Here is
> > what gdb gives me
> >
> > --snip--
> > Reading symbols for shared libraries . done
> > Reading symbols for shared libraries . done
> > Reading symbols for shared li
Erin Sheldon wrote:
> I'm finally getting to this, I'm on the road. Here is
> what gdb gives me
>
> --snip--
> Reading symbols for shared libraries . done
> Reading symbols for shared libraries . done
> Reading symbols for shared libraries .. done
>
> Program received signal EXC_BAD_ACCESS, Coul
I'm finally getting to this, I'm on the road. Here is
what gdb gives me
--snip--
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries .. done
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVA
belinda thom wrote:
> Hi,
>
> I am hopefully almost done w/this exercise, but am uncertain how to
> interpret what the "---, +++, @@ -48,7" etc. I've looked at the
> setupext.py file on my machine but am unclear what changes I need to
> make.
>
> I tried google to find some interpretation,
Hi,
I am hopefully almost done w/this exercise, but am uncertain how to
interpret what the "---, +++, @@ -48,7" etc. I've looked at the
setupext.py file on my machine but am unclear what changes I need to
make.
I tried google to find some interpretation, but was not successful.
I'm somewh
belinda thom wrote:
> Perhaps I should attempt to install matplot lib at this point---I
> don't know. Any idea if the FAILUREs I'm seeing are a problem?
No, they're not. One has been fixed in SVN, and the other two are known bugs
probably related to gfortran.
--
Robert Kern
"I have come to b
Thanks for the Intel update.
I'm doing the same for my PPC (Powerbook, G4, OS X 10.4.8), and have
some failures in scipy's tests. Did you try doing:
>>> import numpy as N
>>> N.test()
and
>>> import scipy as S
>>> S.test()?
For me, the latter one fails (both install and S.test() I/O appe
On 1/8/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> * I use MacPorts to install the other dependencies.
>
> $ sudo port install libjpeg
> $ sudo port install libpng
> $ sudo port install libfreetype
I beg your pardon, this is actually
$ sudo port install jpeg
$ sudo port install libpng
Erin Sheldon wrote:
> I just got a new MacBook Pro, core 2 duo. There is no
> numpy/scipy fink distro for the intels yet so I tried out
> Robert's suggestions above. I installed python 2.5 as
> the base. I can confirm that all is working well for
> numpy and scipy.
>
> Matplotlib compiled, but
On 1/7/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> belinda thom wrote:
>
> > There's other reasons --- mostly curiousity driven --- that motivate
> > me to try a "rawer" (e.g. source, non-pkg based) install:
> >
> > 1) My current kludge only supports TkAgg, so I can't play w/the wx
> > backend at
Robert,
You are incredible! Triple Thanks!
Will begin trying some of this stuff as soon as I've dealt w/hotter
fires.
--b
On Jan 7, 2007, at 10:49 PM, Robert Kern wrote:
> belinda thom wrote:
>
>> There's other reasons --- mostly curiousity driven --- that motivate
>> me to try a "rawer" (e.
belinda thom wrote:
> There's other reasons --- mostly curiousity driven --- that motivate
> me to try a "rawer" (e.g. source, non-pkg based) install:
>
> 1) My current kludge only supports TkAgg, so I can't play w/the wx
> backend at all. Have no idea why
> 2) My current kludge only works w/
Hi,
> I have just completed installing ipython from source by running:
>
>python setup.py install
>
> in a directory from which I downloaded ipython via subversion. That
> was pretty painless (this is my first such install of a relatively
> big program, BTW). If scipy, numpy and matplotlib cou
On Jan 5, 2007, at 6:01 PM, Robert Kern wrote:
> belinda thom wrote:
>> On Jan 5, 2007, at 5:32 PM, Sebastian Haase wrote:
>>
>>> Hi,
>>> All I did is recompiling my (on source code file) C extension. I
>>> made
>>> sure that it was including the current numpy header files.
>>
>> Where are these
package header would usually be found in
PREFIX/include/python2.x
(with PREFIX being something like: /usr/lib/python24 or C:/python24 )
However for obscure reasons in numpy
the header files are in
PREFIX/lib/python2.x/site-packages/numpy/core
You have to "somehow" add this as '-I ' to your
belinda thom wrote:
> On Jan 5, 2007, at 5:32 PM, Sebastian Haase wrote:
>
>> Hi,
>> All I did is recompiling my (on source code file) C extension. I made
>> sure that it was including the current numpy header files.
>
> Where are these files located? What command did you use? (The gorey
> deta
On Jan 5, 2007, at 5:32 PM, Sebastian Haase wrote:
> Hi,
> All I did is recompiling my (on source code file) C extension. I made
> sure that it was including the current numpy header files.
Where are these files located? What command did you use? (The gorey
details would help me quite a bit, a
Hi,
All I did is recompiling my (on source code file) C extension. I made
sure that it was including the current numpy header files.
I did not use anything related to distutils ( no "python setup.py ..." ).
Does that answer your question ?
-Sebastian
On 1/5/07, belinda thom <[EMAIL PROTECTED]>
Sebastian,
I had the same problem awhile back; I'm curious---how'd you fix your
mismatch (i.e. where'd you go to get code, did you run python
setup?, ...). I realize these are very basic questions, but I've
never installed anything from source (aside from using easy_install),
so it would b
You are right again, of course !
Sorry for the noise - I should have just checked the date of my so
file (which is August 15)
At least I understood the "official numpy intention of version 1.0"
right then - just checking ...
Thanks,
Sebastian.
On 1/5/07, Robert Kern <[EMAIL PROTECTED]> wrote:
>
Sebastian Haase wrote:
> Hi!
> After I upgraded from numpy 1.0 to 1.0.1
> I get an abort in a C-module:
>
> RuntimeError: module compiled against version 102 of C-API but this
> version of numpy is 109
> Fatal Python error: numpy.core.multiarray failed to import... exiting.
> /opt/bin/prii
Hi!
After I upgraded from numpy 1.0 to 1.0.1
I get an abort in a C-module:
RuntimeError: module compiled against version 102 of C-API but this
version of numpy is 109
Fatal Python error: numpy.core.multiarray failed to import... exiting.
/opt/bin/priithonN: line 37: 1409 Aborted
27 matches
Mail list logo
