5708534b94
Since the previous call would throw if there was nothing to be assigned
to the value.
Idea from tml.
Used the following script to find places:
git grep -A3 -n UNO_QUERY_THROW | grep -B3 -F 'is()'
Change-Id: I36ba7b00bcd014bdf16c0455ab91056f82194969
Reviewed-on: https://gerrit.libreoffice.org/55417
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
|
||
|---|---|---|
| .. | ||
| demo | ||
| doc | ||
| inc | ||
| qa/pytests | ||
| source | ||
| zipcore | ||
| CustomTarget_python_shell.mk | ||
| CustomTarget_pyuno_pythonloader_ini.mk | ||
| Executable_python.mk | ||
| 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_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.