1acaa577b6
... to set up a fake command line. This is used from pyuno, when invoked from the "python" executable as "import uno". On WNT there is an API to get the actual command line, so just use that even in the "fake" case; on UNX just fake something up. Just for the record the whole osl_setCommandArgs() is called exactly once assumption should work out _unless_ there is a program that uses SAL_MAIN _and_ does a python-level "import uno" _before_ it wants to create a python-based UNO service (via pyuno_loader::CreateInstance), since pyuno already takes care to call Runtime::initialize() at most once. Change-Id: Ifd23de733ea3e6b694d46ab039b6aa4fd3e7fc1b Signed-off-by: Stephan Bergmann <sbergman@redhat.com> |
||
|---|---|---|
| .. | ||
| demo | ||
| doc | ||
| inc/pyuno | ||
| source | ||
| zipcore | ||
| CustomTarget_python_shell.mk | ||
| CustomTarget_zipcore.mk | ||
| Executable_python_wrapper.mk | ||
| Library_pythonloader.mk | ||
| Library_pyuno.mk | ||
| Library_pyuno_wrapper.mk | ||
| Makefile | ||
| Module_pyuno.mk | ||
| Package_python_scripts.mk | ||
| Package_python_shell.mk | ||
| Package_zipcore.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.