Python remote debugging sessions are started in one of three ways: If you have added custom modules to your python site-packages, PYTHONPATH or sys.path with the same name as those imported by pydbgp, the debugger may not work properly. Note: The debugging client relies on certain core python library files (e.g. If the setup is correct, the internal help documentation for running pydbgp is displayed. Now try running this command: pydbgp -help On Linux and Mac OS X, ensure that the pydbgp script is executable by running this command: chmod u+x **path/to**/pydbgp On Windows, also make sure that your PATHEXT environment variable includes. Tip: Placing the pydbgp.py script in a directory that is on your PATH environment variable, makes the script easier to run. This is the main script that you run to start a remote debugging session. Put the bin\pydbgp.py script ( bin/pydbgp on Linux and Mac OS X) somewhere convenient. If this command results in an ImportError then you need to resolve the error before continuing. If this command prints the word “ok”, you can move to the next step. To verify that the setup is correct, run the following command: python -c "import dbgp.client print 'ok'" For example, on Windows, if you copied the files to a directory called C:\debugger, enter the following at the command line: set PYTHONPATH=%PYTHONPATH% C:\debugger Alternatively, you can copy the dbgp directory to a convenient location, and then add that directory to your PYTHONPATH environment variable. You can do this by copying the dbgp directory to the site-packages directory of your Python installation. Set up your Python installation so the dbgp Python package is on your PythonPath.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |