int32 vs uint32 issues with untyped language bindings

[John (J5) Palmieri]

There seems to be an issue with the ability for untyped language
bindings to deal with dbus methods that require uint parameters.  This
showed up in the python bindings when a user tried to use the
ActivateService method call of the org.freedesktop.Dbus service which
requires a uint as its second parameter.  Since python has no concept of
a uint it just sends an int raising a dbus error.  If introspection is
available for the method parameter this can be fixed in the bindings.
If not it can be fixed in dbus so that when validating a uint, positive
integers would be accepted also.  Any suggestions on the right fix for
this?

--
J5