Changes between Version 32 and Version 33 of VirtualEnv


Ignore:
Timestamp:
Aug 27, 2010, 3:52:23 PM (16 years ago)
Author:
Darren Weber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • VirtualEnv

    v32 v33  
    364364spyder
    365365}}}
     366
     367
     368==== TODO: launching spyder within Chimera ====
     369
     370Eric and I tried a few things, including launching Chimera from within spyder and also launching spyder from within Chimera-IDLE using.  For the latter option, we tried:
     371{{{
     372>>> import sys
     373>>> sys.path.append('/home/dweber/src/chimera-virtualenv/lib/python2.7/site-packages/')
     374>>> from spyderlib import spyder
     375>>> spyder.main()
     376}}}
     377
     378Then within the spyder we tried:
     379{{{
     380>>> import sys
     381>>> import os
     382>>> sys.path.append(os.path.join(os.getenv('CHIMERA'), 'share'))
     383>>> sys.path.append(os.path.join(os.getenv('CHIMERA'), 'lib'))
     384>>> sys.path
     385>>> import chimera
     386>>> chimera.runCommand('open 1gcn')
     387}}}
     388
     389This command appeared to run and provide status in the Chimera main window, but the display did not update to show the molecule.  So, we ran into issues with process communication or something.
     390
     391Looking at the Chimera-IDLE extension, we may need to hook some kind of spyder-shell into the chimera.replyobj.  The spyder does have a startup option for --light, which seems to provide a basic shell-like interface.  Of course, that may be no better than IDLE, so that could be pointless.  The goal is to get up all the IDE features of spyder.