[IPython-user] ipython 0.9.rc1: problem with example from the manual during import, using MultiEngineClient
Sat Sep 6 15:46:43 CDT 2008
Hi Brian, thanks for replying. No need to apologise, I appreciate
having access to the software, at all!
My setup is: Access from single core, Intel chip, 32 bit Suse 10.2, to
64 bit Suse10.3 running on a quad core Intel chip, via '$ ssh -X'.
Also, when I execute, '$ python setup.py', I get:
python: 2.5.1 (r251:54863, Sep 21 2007, 22:46:31) [GCC
4.2.1 (SUSE Linux)]
OpenSSL: Not found (required if you want security in the
parallel computing capabilities)
sphinx: Not found (required for building documentation)
pygments: Not found (required for syntax highlighting
nose: Not found (required for running the test suite)
pexpect: no (required for running standalone doctests)
My ~/.ipython directory (on the quad) contains:
db ipythonrc-math ipythonrc-tutorial
history ipythonrc-numeric ipy_user_conf.py
__init__.py ipythonrc-physics ipy_user_conf.pyc
ipy_profile_sh.py ipythonrc-pysh ipy_user_conf.py.original
ipythonrc ipythonrc-scipy log
Um, now for the embarrassing part. I don't know how to uninstall the
packages! I made a bit of a mess while installing, using easy_install
to install ipython-0.9.rc1 (and get ipcluster functionality), YAST
(Suse's package manager) to uninstall 0.8.1 (which failed; 0.8.1 was
still reported on running $ ipython) and finally adjusting PYTHONPATH
until calling $ ipython resulted in :
Python 2.5.1 (r251:54863, Sep 21 2007, 22:46:31)
Type "copyright", "credits" or "license" for more information.
IPython 0.9.rc1 -- An enhanced Interactive Python.
? -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help -> Python's own help system.
object? -> Details about 'object'. ?object also works, ?? prints more.
So, should I start by finding all my ipython directories and deleting
them? Seems a bit crude.....
Thanks for your patience,
Brian Granger wrote:
>> >> Hi everyone, sorry if this is a duplicate post; the original
>> >> appeared, on my machine, under another thread. Sorry for that.
>> >> I'm following the instructions in the Aug 29 2008 manual for
>> >> parallel computing, and have been having some problems; reading
>> >> back through the posts, I've noticed nothing to help (please,
>> >> correct me if I'm wrong!).
> > Sorry about the delay and the confusing docs. I am working on
> > updating them for the 0.9 release. Hopefully that will help
>> >> If I start my cluster with:
>> >> $ ipcluster -n 4 &
>> >> Then, with IPython, 0.9.rc1:
>> >> In : from IPython.kernel import client
>> >> In : tc = client.TaskClient()
>> >> I get:
>> >> ---------------------------------------------------------------------------
>> >> ... traceback information....
>> >> ValueError: not a furl or a file containing a furl:
>> >> /home/m.starnes/.ipython/ipcontroller-tc.furl
> > This should work. Can you tell me more about your setup? OS?
> > Platform? Can you show what is in you ~/.ipython or _ipython
> > directory?
>> >> If I follow the instructions printed by the shell during cluster
>> >> startup:
>> >> In : from ipython1.kernel import client # Differs from the
>> >> manual
>> >> In : mec = client.MultiEngineClient(('127.0.0.1',10105)) #
>> >> Differs.
>> >> All seems well. The same occurs when I follow the 'Quickstart Task
>> >> Farming' section:
>> >> In : tc = client.TaskClient(('127.0.0.1',10105))
> > It this works, then you have:
> > 1. Either both ipython1 and IPython 0.9 installed
> > or
> > 2. Just IPython 0.9 installed
> > I would remove ipython1 and IPython 0.9 and do a reinstall of _just_
> > 0.9 and try again. Also, in 0.9, you don't need to provide (and
> > can't) the ip and port. The two options are:
> > client.TaskClient("path to a furl file") client.TaskClient() #
> > empty - look for the default furl flie.
> > But...there are a few bugs that are in the process of being fixed (we
> > have fixed them, but the fixes aren't in the release candidate or
> > trunk yet).
> > But, this should work. Why don't you clean up your install and give
> > it a try again.
> > Cheers,
> > Brian
More information about the IPython-user