Vincent, Thanks for your reply. Just to clarify: On Dec 30, 2006, at 12:19 PM, Vincent Nijs wrote:

--b,

I had the same problem with ipython on OS X 10.4. I installed it from http://ipython.scipy.org/moin/Download and then everything worked fine, including 'import PyMC'.

Are you using a Mac? Can you please elaborate on "I installed it...and everything worked fine". One of my main points of confusion is why importing PyMC would as a result of (?) reinstalling iPython. Thanks, --b

On Dec 30, 2006, at 12:54 PM, Vincent Nijs wrote:

--b,

Sorry ... I installed everything in the super-pack, including Ipython. Ipython didn't work however (no executable). I could already import PyMC after installing it from the superpack.

Hmmm...I didn't get such luck w/PyMC (or scipy). What python have you got installed?

Installing Ipython from source worked fine.

I use OS X 10.4 (ppc, G4 and a G5).

10.4.<what>? So to summarize, the superpak worked for you, except for not creating the ipython executable. Wish I had such luck. Thanks --b

Vincent, I am now receiving only the errors you reported. Here's the fix (taken from http://www.scipy.org/Installing_SciPy/ Mac_OS_X): ------------ for Power PC machines A binary of g77 (version 3.4) is available from Guarav Khanna's High Performance Computing for Mac OSX site (Download here). Then gunzip g77v3.4-bin.tar.gz (if your browser didn't do so already) and: sudo tar -xvf g77v3.4-bin.tar -C / ------------ the following appeared: ------------ 69 % ll -t /usr/local/lib total 14216 lrwxrwxrwx 1 root wheel 18 Dec 30 15:29 libg2c.0.dylib@ -> libg2c.0.0.0.dylib lrwxrwxrwx 1 root wheel 18 Dec 30 15:29 libg2c.dylib@ -> libg2c.0.0.0.dylib lrwxrwxrwx 1 root wheel 18 Dec 30 15:29 libgcc_s.dylib@ -> libgcc_s.1.0.dylib I then ran the scipy, numpy, and matplotlib superpak packages and was able to run numpy.test() and scipy.test(). It appears this g77 compiler must be installed for the libraries that scipy needs to exist. Would it be possible to ensure that this was the case in side of the super pak itself? If so, it might save others the pain and agony I went through. --b

So you've had no use of matplotlib? Getting that one running in interactive mode was as tricky as the scipy one, IMHO. --b On Dec 31, 2006, at 5:20 AM, Lou Pecora wrote:

I found similar problems with the superpack in that I had to manually install the fortran compiler (using tar command as you already indicated) and manually install iPython. Here's what I did for iPython:

Go to: http://ipython.scipy.org/

Download the ipython-0.7.2.tar.gz version

In the Terminal:

tar -xvzf ipython-0.7.2.tar.gz cd ipython-0.7.2 python setup.py build sudo python setup.py install

iPython works fine as does SciPy, MPL, and NumPy. The latter three installed fine from the superpack.

Using G4 Al Laptop, MacOS X 10.4.8, Python 2.4.

Hope that helps.

I agree that it would be nice to have those superpacks well maintained since bundling can mitigate the painful problems of matching correct versions with all these packages (my main complaint about using Python as a scientific environment -- otherwise I love it).

--- belinda thom <bthom@cs.hmc.edu> wrote:

...

Vincent,

I am now receiving only the errors you reported.

[cut]

-- Lou Pecora My views are my own.

__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user

Hi Lou, On 1/1/07, Lou Pecora <lou_boog2000@yahoo.com> wrote:

I use matplotlib. No real problems there. Just have to remember to set it to interactive for certain things. I think you need to set mpl to use TkAgg for interactive. TKAgg can be invoked in the interpreter by just importing matplotlib and executing matplotlib.use("TKAgg"). I think if you use the wx backend you have to have mpl synchronized with wxPython. Note: WXAgg does *not* work with interactive. I can't recall the problem exactly. Otherwise I have mpl running fine.

I think Belinda's question was regarding the fact that with ipython, if you start it as ipython -pylab it automatically synchronizes with mpl for interactive use, with all (well, except FLTK) the GUI backends. IPython has custom threading support to allow GTK, WX or QT3/4 to correctly work without blocking the input terminal. If I understand correctly, getting the GUI bits to work under OSX has been giving Belinda some grief, unfortunately. Cheers, f

I just tried and am having issues as well. I will check with Jeff to see what is going on. eric Vincent Nijs wrote:

Is there a problem with the scipy website? Connection seems to have been spotty the last couple of days.

Vincent

_______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user

And yet more strangeness...the superpack matplotlib breaks the ability to use pylab: running ipython -pylab produces: <snip> File "/Library/Frameworks/Python.framework/Versions/2.4/lib/ python2.4/site-packages/matplotlib/backends/tkagg.py", line 1, in ? import _tkagg ImportError: Failure linking new module: /Library/Frameworks/ Python.framework/Versions/2.4/lib/python2.4/site-packages/matplotlib/ backends/_tkagg.so: Library not loaded: /usr/local/lib/libfreetype. 6.dylib Referenced from: /Library/Frameworks/Python.framework/Versions/2.4/ lib/python2.4/site-packages/matplotlib/backends/_tkagg.so Reason: image not found Reverting back to the matplotlib at http://www.macpython.org/packages/ py24-fat/index.html allows ipython -pylab to work. I have no idea if mixing and matching parts of superpak with other packages will cause me later problems. I'm curious, Vincent, do you run matplotlib interactively with ipython? Does that piece installed from the superpack work for you? Thanks again, --b