Changes between Version 24 and Version 25 of ChimeraEclipse
- Timestamp:
- Sep 17, 2010, 1:10:05 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ChimeraEclipse
v24 v25 21 21 === Configure !PyDev Preferences === 22 22 23 See this neat [http://www.rose-hulman.edu/class/csse/resources/Eclipse/eclipse-python-configuration.htm step-by-step configuration]. Note especially the section on creating a new project and selecting the language version (2.7) and the interpreter (don't use the default, use the Chimera python install). 24 23 25 Create a new workspace (e.g., Eclipse - File > Switch Workspace > Other) for the new Chimera workspace settings. Then use Window > Preferences to locate the !PyDev panels to setup the "Interpreter - Python" to use the Chimera [http://plato.cgl.ucsf.edu/trac/chimera/attachment/wiki/ChimeraEclipse/Chimera-Eclispe-PyDev-Preferences.png python2.7 interpreter] (be sure to manually add {{{$CHIMERA/share}}} and {{{$CHIMERA/lib}}} to the "system PYTHONPATH" configuration). Then set some [http://plato.cgl.ucsf.edu/trac/chimera/attachment/wiki/ChimeraEclipse/Chimera-Eclispe-PyDev-Preferences-Env.png Chimera environment variables] (the $PATH and $CHIMERA syntax did not work, so these environment settings use full paths; the paths must point to hard-links in the file system, Chimera doesn't work with symbolic-links). Finally, an optional addition is to create a VirtualEnv for Chimera and add the pylint package, then configure the [http://plato.cgl.ucsf.edu/trac/chimera/attachment/wiki/ChimeraEclipse/Chimera-Eclispe-PyDev-Preferences-PyLint.png pylint preferences]. It should be configured now to enable importing Chimera modules and [http://plato.cgl.ucsf.edu/trac/chimera/attachment/wiki/ChimeraEclipse/Chimera-Eclispe-PyDev-Run.png running Chimera]. 24 26 … … 31 33 === Runtime debugging === 32 34 35 Note: this does not address problems with debugging a Tkinter mainloop. 36 33 37 The !PyDev plugin for eclipse has facilities for [http://pydev.org/manual_adv_remote_debugger.html remote debugging] of an active process. To use this facility, startup Chimera as usual and launch the IDLE shell. Startup eclipse and activate the !PyDev debug perspective. Activate the !PyDev [[http://pydev.org/manual_adv_remote_debugger.html remote debugging server]. Using a terminal or file browser, locate the {{{pydevd.py}}} file in your eclipse installation (somewhere in the eclipse plugins; e.g. in a linux terminal try: {{{locate pydevd.py}}}). Then, within IDLE, enter the following to enable remote debugging within the eclipse debug perspective: 34 38 {{{ … … 39 43 pydevd.settrace() 40 44 }}} 41 In the eclipse console, try {{{print "Hello there!"}}} and see if it appears in the IDLE shell. If it does, your hooked into Chimera from eclipse and you have access to allthe object inspection features of the !PyDev debugger.45 In the eclipse console, try {{{print "Hello there!"}}} and see if it appears in the IDLE shell. If it does, your hooked into Chimera from eclipse and you have access to the object inspection features of the !PyDev debugger. 42 46
![[Chimera Issue Tracking System]](/trac/chimera/chrome/site/chimera_logo.png)