c16158772d
Renaming all README files for all top level modules to README.md, applying no content change at this stage to be able to track history of the files. These files should be edited to use correct Markdown syntax later. Change-Id: I542fa3f3d32072156f16eaad2211a397cc212665 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/112977 Tested-by: Jenkins Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com> |
||
|---|---|---|
| .. | ||
| demo | ||
| doc | ||
| inc | ||
| qa/pytests | ||
| source | ||
| zipcore | ||
| CustomTarget_python_shell.mk | ||
| CustomTarget_pyuno_pythonloader_ini.mk | ||
| Executable_python.mk | ||
| IwyuFilter_pyuno.yaml | ||
| Library_pythonloader.mk | ||
| Library_pyuno.mk | ||
| Library_pyuno_wrapper.mk | ||
| Makefile | ||
| Module_pyuno.mk | ||
| Package_python_scripts.mk | ||
| Package_python_shell.mk | ||
| Package_pyuno_pythonloader_ini.mk | ||
| PythonTest_pyuno_pytests_insertremovecells.mk | ||
| PythonTest_pyuno_pytests_testcollections.mk | ||
| PythonTest_pyuno_pytests_testssl.mk | ||
| Rdb_pyuno.mk | ||
| README.md | ||
UNO bindings for the Python programming language.
To have much joy debugging python extensions you need to: a) edit pythonloader.py in your install setting DEBUG=1 at the top b) touch pyuno/source/module/pyuno_runtime.cxx and 'make debug=true' in pyuno
Then you'll start to see your exceptions on the console instead of them getting lost at the UNO interface.
Python also comes with a gdb script libpython$(PYTHON_VERSION_MAJOR).$(PYTHON_VERSION_MINOR)m.so.1.0-gdb.py that is copied to instdir and will be auto-loaded by gdb; it provides commands like "py-bt" to get a python-level backtrace, and "py-print" to print python variables.
Another way to debug Python code is to use pdb: edit some initialization function to insert "import pdb; pdb.set_trace()" (somewhere so that it is executed early), then run soffice from a terminal and a command-line python debugger will appear where you can set python-level breakpoints.