Hi,
- One thing that I find disappointing is the fact that the UNO
introspection capabilities are not (as far as I understand, but again,
I am very new in this code) very well reflected in the pyuno module (at
least the python way).
- Is there a technical reason (but the lack of dev time) why UNO types,
classes, services and interfaces are not exported in Python as types and
classes (rather than instances of an obscure class like it is the case
for now)?
the python proxy for UNO objects currently does not support the
__members__, __dict__, etc. (see pyuno/source/module/pyuno.cxx
PyUNO_getattr), this is the place, where improvement should take place.
Note that the __members__ attribute currently is even buggy implemented,
using it will lead to a crash (see
http://qa.openoffice.org/issues/show_bug.cgi?id=47270).
Main reason for not supporting this attributes is actually my lack of
knowledge of these python internas. Which attributes should be supported
from your point of view ?
Similar things hold for structs and exception (see
pyuno/source/module/pyuno_except.cxx).
Bye,
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
