Split The Signature Module After The Project Split

The PySide project has been split into three pieces, including
Shiboken. This had far-reaching consequences for the signature project.

Shiboken can be run together with PySide or alone,
with tests or without. In every configuration, the signature
module has to work correctly.

During tests, the shiboken binary also hides the shiboken module,
and we had to use extra efforts to always guarantee the accessibility
of all signature modules.

This commit is the preparation for typeerrors implemented with the
signature module. It has been split off because the splitting
is not directly related, besides these unawaited consequences.

I re-added and corrected voidptr_test and simplified the calls.
Remark.. We should rename shiboken to Shiboken in all imports.

I also simplified initialization. After "from PySide2 import QtCore",
now a simple access like "type.__signature__" triggers initialization.

Further, I removed all traces of "signature_loader" and allowed
loading everything from PySide2.support.signature, again. The
loader is now needed internally, only.

Also, moved the type patching into FinishSignatureInitialization
to support modules with no classes at all.

The "testbinding" problem was finally identified as a name clash
when the same function is also a signal. A further investigation
showed that there exists also a regular PySide method with
that problem. The test was extended to all methods, and it
maps now all these cases to "{name}.overload".

Updated the included typing27.py from https://pypi.org/project/typing/
from version 3.6.2 to version 3.6.6 .

Task-number: PYSIDE-749
Change-Id: Ie33b8c6b0df5640212f8991539088593a041a05c
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>

0 files changed, 0 insertions, 0 deletions