Remove unnecessary "setup.py" mechanism for initializing extensions

There already is the requirements.txt mechanism that takes care of pip
installing in the right way.

Setup for which this is not sufficient should be possible to do in the
initialization code of the extension directly. Additionally the provided
example was broken (e.g. didn't work with spaces in paths), and the
whole mechanism had the encapsulation problem that the extensions
themselves had before they were made modules/packages.

Change-Id: I8692e26e65ec667267c7918e6edbd32f55534bc8
Reviewed-by: Eike Ziller <eike.ziller@qt.io>

1 files changed, 4 insertions, 7 deletions

diff --git a/README.md b/README.md
index 657bf9b..4e3886c 100644
--- a/README.md
+++ b/README.md
@@ -125,16 +125,13 @@ The following process allows the plugin to work:
 
  1. At compile time, Shiboken generates a huge amount of C++ code that
     allows a few classes from the Core plugin and utils library to be
-     accessed from Python.
+    accessed from Python.
  2. When QtCreator is executed, the C++ plugin searches the standard
     QtCreator plugin directories for a directory named `python`, the
     first directory found is the Python extension directory.
-    - Now, each package in this directory represents it's own Python extension.
-      For each package the C++ plugin checks whether it
-      contains a `setup.py`. If it does, this setup script is executed.
-    - After all the setup scripts have been executed, each package is loaded
-      with `import`, which executes the initialization code in its
-      `__init__.py`.
+    Each python package in this directory represents it's own Python extension.
+    Each package is loaded with `import`, which executes the initialization
+    code in its `__init__.py`.
  3. Now all Python extensions have registered their actions / menus / etc.,
     which can be triggered from the QtCreator interface.