![]() ![]() Double-clicking an existing breakpoint will remove it. In a line with an existing breakpoint Ctrl+F10 will be able to remove the breakpoint, disable it and edit its properties (which can be used to provide conditions for the breakpoint to be hit). To add breakpoints, you can double click the left bar or use Ctrl+F10 > Add breakpoint. Hover showing the selected expression evaluation.Temporary display for selection: Ctrl+Shift+D.You can go to the menu with keybindings ( Alt+R, then 'T' regular run or 'H' for debug run) and choose some existing launch to be run. To do that, open the eclipse preferences ( window > preferences) and check "Always launch previously launched application", that way, when you use F11, your last launch will be repeated in debug mode and with Ctrl+F11, it'll be relaunched in the regular mode.Īnother option would be running the last launch from the menu. If you use the F9 and Ctrl+F9 keybindings or launch through the context menu, usually you'll also want to check the default eclipse preferences so that Ctrl+F11 and F11 will run your last configuration (otherwise, they'll bring a dialog to run/debug your current editor, which is mostly what's already given by PyDev through F9 and Ctrl+F9). See: `Rerun Last Launch (regular or debug mode)`_ Rerun Last Launch (regular or debug mode) To run in debug mode, you can use the context menu, where you can choose how you want to make the debug (note that in that way, you could debug a python project with a jython interpreter)Īnother option would be running the last launch in debug mode. Explicitly selecting the class/tests to run will run those tests.Extending the filter and pressing 'Enter' will run the filtered tests.If you use unit-tests, and want to run only a single unit-test or a few unit-tests of a module, you can use the Ctrl+F9 keybinding, which will open a tree where you can choose which test(s) you want to run: Through that command, PyDev will create/reuse a launch config to run the current editor based on the current settings of the project (i.e.: if the project is configured as IronPython, it'll use an IronPython interpreter).Īnother option would be running using the context menu, where you can choose how you want to make the run (in that way, you could run a python project with a jython interpreter) The easiest way of launching a python file from PyDev is opening an editor and using the F9 keybinding. I was really hoping to get this working as it would make debugging a lot easier, without having to hard-code references for parameters to get the IDE to debug in stand-alone mode.Launching/Debugging Python scripts Regular Launch But when I try to run a script tool in debug mode (right-click on a script tool, then select "Debug"), the script runs fine, but the IDE never launches. ![]() I've tried both PythonWin and PyScripter and I can edit python scripts through the ArcGIS interface (right-click on a script tool, then select "Edit"). I have not been able to get the debugger to attach to the ArcMap process, however. I've added the path to the EXE for the IDE in the Geoprocessing Options dialog for both "Editor" and "Debugger". The relevant section is under "Execute and debug your tool". I've reviewed this help document, which seems to suggest that you can run a debugger/IDE such as PythonWin or PyScripter when testing code through the ArcToolbox interface: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |