office-gobmx/pyuno
Stephan Bergmann e3aef4dc7c Some simplifications, using UNO_QUERY_THROW
Change-Id: Ib973a403a830a3ecf8e57a5e70a581ba06f96a05
Reviewed-on: https://gerrit.libreoffice.org/34264
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2017-02-15 14:18:17 +00:00
..
demo
doc
inc
qa/pytests
source Some simplifications, using UNO_QUERY_THROW 2017-02-15 14:18:17 +00:00
zipcore Remove MinGW support 2017-02-10 18:01:27 +00:00
CustomTarget_python_shell.mk
CustomTarget_pyuno_pythonloader_ini.mk Remove MinGW support 2017-02-10 18:01:27 +00:00
Executable_python.mk
Library_pythonloader.mk
Library_pyuno.mk
Library_pyuno_wrapper.mk
Makefile
Module_pyuno.mk Remove MinGW support 2017-02-10 18:01:27 +00:00
Package_python_scripts.mk
Package_python_shell.mk
Package_pyuno_pythonloader_ini.mk
PythonTest_pytests.mk
PythonTest_pyuno_pytests_insertremovecells.mk
PythonTest_pyuno_pytests_ssl.mk
PythonTest_pyuno_pytests_testcollections.mk
Rdb_pyuno.mk
README

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.