I removed the dbus-python bug task because this is a deliberate decision in dbus-python, not a bug. Specifically, this comment in message-append.c sheds some light:
/* No items, so fail. Or should we guess "a{vv}"? */
I actually think dbus-python is probably doing the right thing by refusing to guess the signature of an empty dictionary. It's probably a bug that the documentation doesn't describe this, and I will file such a documentation bug upstream.
I removed the dbus-python bug task because this is a deliberate decision in dbus-python, not a bug. Specifically, this comment in message-append.c sheds some light:
/* No items, so fail. Or should we guess "a{vv}"? */
I actually think dbus-python is probably doing the right thing by refusing to guess the signature of an empty dictionary. It's probably a bug that the documentation doesn't describe this, and I will file such a documentation bug upstream.