[Ipython-tickets] [IPython] #160: IPython1 remote controller problems triggered by mlabwrap

[IPython]

#160: IPython1 remote controller problems triggered by mlabwrap
--------------------+-------------------------------------------------------
 Reporter:  jitter  |        Owner:  bgranger
     Type:  defect  |       Status:  assigned
 Priority:  normal  |    Milestone:          
Component:  saw     |      Version:          
 Severity:  normal  |   Resolution:          
 Keywords:          |  
--------------------+-------------------------------------------------------
Comment (by jitter):

 Hi!

 I updated both ipython and ipython1 (saw branch) and tried again. Albeit
 the error message is a lot more informative the behavior stayed the same.
 I.e. when importing mlabwrap one time only I get a NameError exception:


 {{{
 Traceback (most recent call last):
   File "testmlabwrap.py", line 61, in ?
     testmlabwrap()
   File "testmlabwrap.py", line 34, in testmlabwrap
     remoteController.executeAll("mlabwrap.mlab.help()")
   File "/usr/lib64/python2.4/site-
 packages/ipython1-0.9alpha2-py2.4.egg/ipython1/kernel/multienginexmlrpc.py",
 line 533, in executeAll
     return self.execute('all', lines, block)
   File "/usr/lib64/python2.4/site-
 packages/ipython1-0.9alpha2-py2.4.egg/ipython1/kernel/multienginexmlrpc.py",
 line 520, in execute
     result = self._executeRemoteMethod(self._server.execute,
 self._clientID, localBlock, targets, lines)
   File "/usr/lib64/python2.4/site-
 packages/ipython1-0.9alpha2-py2.4.egg/ipython1/kernel/multienginexmlrpc.py",
 line 390, in _executeRemoteMethod
     result = self._unpackageResult(rawResult)
   File "/usr/lib64/python2.4/site-
 packages/ipython1-0.9alpha2-py2.4.egg/ipython1/kernel/multienginexmlrpc.py",
 line 399, in _unpackageResult
     return self._returnOrRaise(result)
   File "/usr/lib64/python2.4/site-
 packages/ipython1-0.9alpha2-py2.4.egg/ipython1/kernel/multienginexmlrpc.py",
 line 403, in _returnOrRaise
     result.raiseException()
   File "/usr/lib64/python2.4/site-packages/twisted/python/failure.py",
 line 259, in raiseException
     raise self.type, self.value, self.tb
 NameError:
 ***************************************************************************
 An exception occurred in the IPython Interpreter due to a user action.
 This usually means that user code has a problem in it somewhere.

 engine: 2
 method: execute(lines)
 lines = mlabwrap.mlab.help()

 A full traceback from the actual interpreter:
 ---------------------------------------------------------------------------
 NameError                                 Traceback (most recent call
 last)


 NameError:
 ***************************************************************************
 }}}


 Using the workaround mentioned above (a second "import mlabwrap"
 statement) it works nicely.

 Regarding your comment about the cluster not being ready: hmm, os.system()
 blocks until ipcluster is done, so this shouldn't be a problem. I'm using
 almost identical code in my SciPy-only scripts that are executed on the
 cluster and it works reliably for me.

 Thanks,
 jitter

-- 
Ticket URL: <http://projects.scipy.org/ipython/ipython/ticket/160#comment:4>
IPython <http://ipython.scipy.org>
The IPython interactive Python system