Entry step for renaming PyTQt module libraries from qt* to tqt*.

Signed-off-by: Slávek Banko <slavek.banko@axis.cz>

12 files changed, 61 insertions, 61 deletions

diff --git a/doc/html/_sources/build_system.txt b/doc/html/_sources/build_system.txt
index fda9172..3b95af5 100644
--- a/doc/html/_sources/build_system.txt
+++ b/doc/html/_sources/build_system.txt
@@ -12,7 +12,7 @@ supports over 50 different platform/compiler combinations.
 
 The build system is implemented as a pure Python module called :mod:`sipconfig`
 that contains a number of classes and functions.  Using this module you can
-write bespoke configuration scripts (e.g. PyQt's ``configure.py``) or use it
+write bespoke configuration scripts (e.g. PyTQt's ``configure.py``) or use it
 with other Python based build systems (e.g.
 `Distutils <http://www.python.org/sigs/distutils-sig/distutils.html>`_ and
 `SCons <http://www.scons.org>`_).
@@ -20,17 +20,17 @@ with other Python based build systems (e.g.
 An important feature of SIP is the ability to generate bindings that are built
 on top of existing bindings.  For example, both
 `PyKDE <http://www.riverbankcomputing.com/software/pytde/>`_ and
-`PyQwt <http://pyqwt.sourceforge.net/>`_ are built on top of PyQt but all three
-packages are maintained by different developers.  To make this easier PyQt
-includes its own configuration module, ``pyqtconfig``, that contains additional
+`PyQwt <http://pyqwt.sourceforge.net/>`_ are built on top of PyTQt but all three
+packages are maintained by different developers.  To make this easier PyTQt
+includes its own configuration module, ``pytqtconfig``, that contains additional
 classes intended to be used by the configuration scripts of bindings built on
-top of PyQt.  The SIP build system includes facilities that do a lot of the
+top of PyTQt.  The SIP build system includes facilities that do a lot of the
 work of creating these additional configuration modules.
 
 
 .. function:: create_config_module(module, template, content[, macros=None])
 
-    This creates a configuration module (e.g. ``pyqtconfig``) from a template
+    This creates a configuration module (e.g. ``pytqtconfig``) from a template
     file and a string.
 
     :param module:
@@ -377,7 +377,7 @@ work of creating these additional configuration modules.
 
         A string that will remove a file.
 
-    .. method:: __init__(configuration[, console=0[, qt=0[, opengl=0[, python=0[, threaded=0[, warnings=None[, debug=0[, dir=None[, makefile="Makefile"[, installs=None[, universal=None[, arch=None]]]]]]]]]]]])
+    .. method:: __init__(configuration[, console=0[, tqt=0[, opengl=0[, python=0[, threaded=0[, warnings=None[, debug=0[, dir=None[, makefile="Makefile"[, installs=None[, universal=None[, arch=None]]]]]]]]]]]])
 
         :param configuration:
             the current configuration and is an instance of the
@@ -385,8 +385,8 @@ work of creating these additional configuration modules.
         :param console:
             is set if the target is a console (rather than GUI) target.  This
             only affects Windows and is ignored on other platforms.
-        :param qt:
-            is set if the target uses Qt.  For Qt v4 a list of Qt libraries may
+        :param tqt:
+            is set if the target uses TQt.  For Qt v4 a list of Qt libraries may
             be specified and a simple non-zero value implies QtCore and QtGui.
         :param opengl:
             is set if the target uses OpenGL.
@@ -394,7 +394,7 @@ work of creating these additional configuration modules.
             is set if the target uses Python.h.
         :param threaded:
             is set if the target requires thread support.  It is set
-            automatically if the target uses Qt and Qt has thread support
+            automatically if the target uses TQt and TQt has thread support
             enabled.
         :param warnings:
             is set if compiler warning messages should be enabled.  The default
@@ -572,7 +572,7 @@ work of creating these additional configuration modules.
             :ref:`ref-builtin`).
         :param console:
             see :meth:`sipconfig.Makefile.__init__`.
-        :param qt:
+        :param tqt:
             see :meth:`sipconfig.Makefile.__init__`.
         :param opengl:
             see :meth:`sipconfig.Makefile.__init__`.
@@ -686,7 +686,7 @@ work of creating these additional configuration modules.
 
     This class encapsulates a Makefile to build an executable program.
 
-    .. method:: __init__(configuration[, build_file=None[, install_dir=None[, console=0[, qt=0[, opengl=0[, python=0[, threaded=0[, warnings=None[, debug=0[, dir=None[, makefile="Makefile"[, installs=None[, universal=None[, arch=None]]]]]]]]]]]]]])
+    .. method:: __init__(configuration[, build_file=None[, install_dir=None[, console=0[, tqt=0[, opengl=0[, python=0[, threaded=0[, warnings=None[, debug=0[, dir=None[, makefile="Makefile"[, installs=None[, universal=None[, arch=None]]]]]]]]]]]]]])
 
         :param configuration:
             see :meth:`sipconfig.Makefile.__init__`.
@@ -698,7 +698,7 @@ work of creating these additional configuration modules.
             optionally installed.
         :param console:
             see :meth:`sipconfig.Makefile.__init__`.
-        :param qt:
+        :param tqt:
             see :meth:`sipconfig.Makefile.__init__`.
         :param opengl:
             see :meth:`sipconfig.Makefile.__init__`.
@@ -810,7 +810,7 @@ work of creating these additional configuration modules.
             see :meth:`sipconfig.ModuleMakefile.__init__`.
         :param console:
             see :meth:`sipconfig.Makefile.__init__`.
-        :param qt:
+        :param tqt:
             see :meth:`sipconfig.Makefile.__init__`.
         :param opengl:
             see :meth:`sipconfig.Makefile.__init__`.
diff --git a/doc/html/_sources/c_api.txt b/doc/html/_sources/c_api.txt
index 66e0af2..c1cb25a 100644
--- a/doc/html/_sources/c_api.txt
+++ b/doc/html/_sources/c_api.txt
@@ -1696,7 +1696,7 @@ name prefixed by ``sip``.  For example, the derived class for class ``Klass``
 is ``sipKlass``.
 
 If a C++ class doesn't have any virtual or protected methods in it or any of
-it's super-class hierarchy, or does not emit any Qt Q_SIGNALS, then a derived
+it's super-class hierarchy, or does not emit any TQt Q_SIGNALS, then a derived
 class is not generated.
 
 Most of the time handwritten code should ignore the derived classes.  The only
diff --git a/doc/html/_sources/command_line.txt b/doc/html/_sources/command_line.txt
index 9c50cf4..8a1db23 100644
--- a/doc/html/_sources/command_line.txt
+++ b/doc/html/_sources/command_line.txt
@@ -24,8 +24,8 @@ The full set of command line options is:
 
 .. cmdoption:: -a <FILE>
 
-    The name of the QScintilla API file to generate.  This file contains a
-    description of the module API in a form that the QScintilla editor
+    The name of the TQScintilla API file to generate.  This file contains a
+    description of the module API in a form that the TQScintilla editor
     component can use for auto-completion and call tips.  (The file may also be
     used by the SciTE editor but must be sorted first.)  By default the file is
     not generated.
diff --git a/doc/html/_sources/incompatibilities.txt b/doc/html/_sources/incompatibilities.txt
index a006e4f..df5c2c4 100644
--- a/doc/html/_sources/incompatibilities.txt
+++ b/doc/html/_sources/incompatibilities.txt
@@ -70,10 +70,10 @@ In addition the :option:`-a` command line option to :file:`configure.py` has
 been removed.
 
 
-Removal of PyQt-specific Features
+Removal of PyTQt-specific Features
 *********************************
 
-The following PyQt-specific support functions have been removed.
+The following PyTQt-specific support functions have been removed.
 
 - :cfunc:`sipConnectRx()`
 
diff --git a/doc/html/_sources/introduction.txt b/doc/html/_sources/introduction.txt
index 8488b6f..e89f48e 100644
--- a/doc/html/_sources/introduction.txt
+++ b/doc/html/_sources/introduction.txt
@@ -4,8 +4,8 @@ Introduction
 This is the reference guide for SIP 4.10.5.  SIP is a tool for
 automatically generating `Python <http://www.python.org>`__ bindings for C and
 C++ libraries.  SIP was originally developed in 1998 for
-`PyQt <http://www.riverbankcomputing.com/software/pyqt>`__ - the Python
-bindings for the Qt GUI toolkit - but is suitable for generating bindings for
+`PyTQt <http://www.riverbankcomputing.com/software/pytqt>`__ - the Python
+bindings for the TQt GUI toolkit - but is suitable for generating bindings for
 any C or C++ library.
 
 This version of SIP generates bindings for Python v2.3 or later, including
@@ -156,14 +156,14 @@ SIP comprises a number of different components.
   :ref:`ref-distutils`.
 
 
-Qt Support
+TQt Support
 ----------
 
 SIP has specific support for the creation of bindings based on Nokia's Qt
 toolkit.
 
 The SIP code generator understands the signal/slot type safe callback mechanism
-that Qt uses to connect objects together.  This allows applications to define
+that TQt uses to connect objects together.  This allows applications to define
 new Python Q_SIGNALS, and allows any Python callable object to be used as a slot.
 
-SIP itself does not require Qt to be installed.
+SIP itself does not require TQt to be installed.
diff --git a/doc/html/_sources/specification_files.txt b/doc/html/_sources/specification_files.txt
index ff352f4..baa18f5 100644
--- a/doc/html/_sources/specification_files.txt
+++ b/doc/html/_sources/specification_files.txt
@@ -268,7 +268,7 @@ file.
     *argument* ::= [
             *type* [*name*] [*argument-annotations*] [*default-value*] |
             :stype:`SIP_ANYSLOT` [*default-value*] |
-            :stype:`SIP_QOBJECT` |
+            :stype:`SIP_TQOBJECT` |
             :stype:`SIP_RXOBJ_CON` |
             :stype:`SIP_RXOBJ_DIS` |
             :stype:`SIP_SIGNAL` [*default-value*] |
@@ -422,24 +422,24 @@ This is a ``PyObject *`` that is a Python tuple object.
 This is a ``PyObject *`` that is a Python type object.
 
 
-.. sip-type:: SIP_QOBJECT
+.. sip-type:: SIP_TQOBJECT
 
-This is a ``QObject *`` that is a C++ instance of a class derived from Qt's
-``QObject`` class.
+This is a ``TQObject *`` that is a C++ instance of a class derived from TQt's
+``TQObject`` class.
 
 
 .. sip-type:: SIP_RXOBJ_CON
 
-This is a ``QObject *`` that is a C++ instance of a class derived from Qt's
-``QObject`` class.  It is used as the type of the receiver instead of ``const
-QObject *`` in functions that implement a connection to a slot.
+This is a ``TQObject *`` that is a C++ instance of a class derived from TQt's
+``TQObject`` class.  It is used as the type of the receiver instead of ``const
+TQObject *`` in functions that implement a connection to a slot.
 
 
 .. sip-type:: SIP_RXOBJ_DIS
 
-This is a ``QObject *`` that is a C++ instance of a class derived from Qt's
-``QObject`` class.  It is used as the type of the receiver instead of ``const
-QObject *`` in functions that implement a disconnection from a slot.
+This is a ``TQObject *`` that is a C++ instance of a class derived from TQt's
+``TQObject`` class.  It is used as the type of the receiver instead of ``const
+TQObject *`` in functions that implement a disconnection from a slot.
 
 
 .. sip-type:: SIP_SIGNAL
@@ -468,7 +468,7 @@ signal to a slot.  The signal is emitted when the keyboard accelerator is
 activated and it has a single integer argument that is the ID of the
 accelerator.  The C++ signature is::
 
-    bool connectItem(int id, const QObject *receiver, const char *member);
+    bool connectItem(int id, const TQObject *receiver, const char *member);
 
 The corresponding SIP specification is::
 
diff --git a/doc/html/_sources/using.txt b/doc/html/_sources/using.txt
index ff121ce..427888f 100644
--- a/doc/html/_sources/using.txt
+++ b/doc/html/_sources/using.txt
@@ -193,7 +193,7 @@ A More Complex C++ Example
 --------------------------
 
 In this last example we will wrap a fictional C++ library that contains a class
-that is derived from a Qt class.  This will demonstrate how SIP allows a class
+that is derived from a TQt class.  This will demonstrate how SIP allows a class
 hierarchy to be split across multiple Python extension modules, and will
 introduce SIP's versioning system.
 
diff --git a/doc/html/build_system.html b/doc/html/build_system.html
index 772457e..72cab70 100644
--- a/doc/html/build_system.html
+++ b/doc/html/build_system.html
@@ -65,14 +65,14 @@ on top of existing bindings.  For example, both
 <a class="reference external" href="http://www.riverbankcomputing.com/software/pytde/">PyKDE</a> and
 <a class="reference external" href="http://pyqwt.sourceforge.net/">PyQwt</a> are built on top of PyTQt but all three
 packages are maintained by different developers.  To make this easier PyTQt
-includes its own configuration module, <tt class="docutils literal"><span class="pre">pyqtconfig</span></tt>, that contains additional
+includes its own configuration module, <tt class="docutils literal"><span class="pre">pytqtconfig</span></tt>, that contains additional
 classes intended to be used by the configuration scripts of bindings built on
 top of PyTQt.  The SIP build system includes facilities that do a lot of the
 work of creating these additional configuration modules.</p>
 <dl class="function">
 <dt id="sipconfig.create_config_module">
 <tt class="descclassname">sipconfig.</tt><tt class="descname">create_config_module</tt><big>(</big><em>module</em>, <em>template</em>, <em>content</em><span class="optional">[</span>, <em>macros=None</em><span class="optional">]</span><big>)</big><a class="headerlink" href="#sipconfig.create_config_module" title="Permalink to this definition">¶</a></dt>
-<dd><p>This creates a configuration module (e.g. <tt class="docutils literal"><span class="pre">pyqtconfig</span></tt>) from a template
+<dd><p>This creates a configuration module (e.g. <tt class="docutils literal"><span class="pre">pytqtconfig</span></tt>) from a template
 file and a string.</p>
 <table class="docutils field-list" frame="void" rules="none">
 <col class="field-name" />
diff --git a/doc/html/directives.html b/doc/html/directives.html
index 1e8ee1f..b565367 100644
--- a/doc/html/directives.html
+++ b/doc/html/directives.html
@@ -685,7 +685,7 @@ modules, that doesn&#8217;t have an explicit meta-type.</p>
 meta-type used by a particular C/C++ type.</p>
 <p>See the section <a class="reference external" href="using.html#ref-types-metatypes"><em>Types and Meta-types</em></a> for more details.</p>
 <p>For example:</p>
-<div class="highlight-python"><pre>%DefaultMetatype PyTQt4.TQtCore.pyqtWrapperType</pre>
+<div class="highlight-python"><pre>%DefaultMetatype PyTQt4.TQtCore.pytqtWrapperType</pre>
 </div>
 <dl class="directive">
 <dt id="directive-%DefaultSupertype">
@@ -1144,7 +1144,7 @@ containing the <a class="reference internal" href="#directive-%Import"><tt class
 fails then SIP prepends <em>filename</em> with each of the directories, in turn,
 specified by the <tt class="docutils literal"><span class="pre">-I</span></tt> command line option.</p>
 <p>For example:</p>
-<div class="highlight-python"><pre>%Import qt/qtmod.sip</pre>
+<div class="highlight-python"><pre>%Import tqt/tqtmod.sip</pre>
 </div>
 <dl class="directive">
 <dt id="directive-%Include">
@@ -1548,7 +1548,7 @@ module.</p>
 changes don&#8217;t affect the exported API, but it is good practice to change the
 version number anyway.</p>
 <p>For example:</p>
-<div class="highlight-python"><pre>%Module qt 5</pre>
+<div class="highlight-python"><pre>%Module tqt 5</pre>
 </div>
 <dl class="directive">
 <dt id="directive-%ModuleCode">
diff --git a/doc/html/incompatibilities.html b/doc/html/incompatibilities.html
index e3f8998..9140bc9 100644
--- a/doc/html/incompatibilities.html
+++ b/doc/html/incompatibilities.html
@@ -101,8 +101,8 @@ from <a title="sipBuildResult" class="reference external" href="c_api.html#sipBu
 <p>In addition the <a class="reference external" href="command_line.html#cmdoption-sip-a"><em class="xref">-a</em></a> command line option to <tt class="docutils literal"><span class="pre">configure.py</span></tt> has
 been removed.</p>
 </div>
-<div class="section" id="removal-of-pyqt-specific-features">
-<h3>Removal of PyTQt-specific Features<a class="headerlink" href="#removal-of-pyqt-specific-features" title="Permalink to this headline">¶</a></h3>
+<div class="section" id="removal-of-pytqt-specific-features">
+<h3>Removal of PyTQt-specific Features<a class="headerlink" href="#removal-of-pytqt-specific-features" title="Permalink to this headline">¶</a></h3>
 <p>The following PyTQt-specific support functions have been removed.</p>
 <ul class="simple">
 <li><tt class="xref docutils literal"><span class="pre">sipConnectRx()</span></tt></li>
@@ -210,7 +210,7 @@ still supported).</p>
 <li><a class="reference external" href="#truediv">__truediv__</a></li>
 <li><a class="reference external" href="#sipwrapper-user-member">sipWrapper user Member</a></li>
 <li><a class="reference external" href="#removal-of-previously-deprecated-features">Removal of Previously Deprecated Features</a></li>
-<li><a class="reference external" href="#removal-of-pyqt-specific-features">Removal of PyTQt-specific Features</a></li>
+<li><a class="reference external" href="#removal-of-pytqt-specific-features">Removal of PyTQt-specific Features</a></li>
 <li><a class="reference external" href="#id1">Newly Deprecated Features</a></li>
 </ul>
 </li>
diff --git a/doc/html/introduction.html b/doc/html/introduction.html
index 70fce7f..6b85581 100644
--- a/doc/html/introduction.html
+++ b/doc/html/introduction.html
@@ -53,7 +53,7 @@
 <p>This is the reference guide for SIP 4.10.5.  SIP is a tool for
 automatically generating <a class="reference external" href="http://www.python.org">Python</a> bindings for C and
 C++ libraries.  SIP was originally developed in 1998 for
-<a class="reference external" href="http://www.riverbankcomputing.com/software/pyqt">PyTQt</a> - the Python
+<a class="reference external" href="http://www.riverbankcomputing.com/software/pytqt">PyTQt</a> - the Python
 bindings for the TQt GUI toolkit - but is suitable for generating bindings for
 any C or C++ library.</p>
 <p>This version of SIP generates bindings for Python v2.3 or later, including
@@ -162,7 +162,7 @@ needed to build the extension module.  It is covered in detail in
 <a class="reference external" href="distutils.html#ref-distutils"><em>Building Your Extension with distutils</em></a>.</li>
 </ul>
 </div>
-<div class="section" id="qt-support">
+<div class="section" id="tqt-support">
 <h2>TQt Support<a class="headerlink" href="#qt-support" title="Permalink to this headline">¶</a></h2>
 <p>SIP has specific support for the creation of bindings based on Nokia&#8217;s TQt
 toolkit.</p>
diff --git a/doc/html/using.html b/doc/html/using.html
index f58e316..ea519af 100644
--- a/doc/html/using.html
+++ b/doc/html/using.html
@@ -343,7 +343,7 @@ copy constructor when it can never be called from Python?  The answer is to
 prevent the automatic generation of a public copy constructor.</p>
 <p>We now look at the <tt class="docutils literal"><span class="pre">configure.py</span></tt> script.  This is a little different to the
 script in the previous examples for two related reasons.</p>
-<p>Firstly, PyTQt includes a pure Python module called <tt class="docutils literal"><span class="pre">pyqtconfig</span></tt> that extends
+<p>Firstly, PyTQt includes a pure Python module called <tt class="docutils literal"><span class="pre">pytqtconfig</span></tt> that extends
 the SIP build system for modules, like our example, that build on top of PyTQt.
 It deals with the details of which version of TQt is being used (i.e. it
 determines what the correct tags are) and where it is installed.  This is
@@ -355,23 +355,23 @@ life easier for them.</p>
 <p>Now we have two scripts.  First the <tt class="docutils literal"><span class="pre">configure.py</span></tt> script:</p>
 <div class="highlight-python"><div class="highlight"><pre><span class="kn">import</span> <span class="nn">os</span>
 <span class="kn">import</span> <span class="nn">sipconfig</span>
-<span class="kn">from</span> <span class="nn">PyTQt4</span> <span class="kn">import</span> <span class="n">pyqtconfig</span>
+<span class="kn">from</span> <span class="nn">PyTQt4</span> <span class="kn">import</span> <span class="n">pytqtconfig</span>
 
 <span class="c"># The name of the SIP build file generated by SIP and used by the build</span>
 <span class="c"># system.</span>
 <span class="n">build_file</span> <span class="o">=</span> <span class="s">&quot;hello.sbf&quot;</span>
 
 <span class="c"># Get the PyTQt configuration information.</span>
-<span class="n">config</span> <span class="o">=</span> <span class="n">pyqtconfig</span><span class="o">.</span><span class="n">Configuration</span><span class="p">()</span>
+<span class="n">config</span> <span class="o">=</span> <span class="n">pytqtconfig</span><span class="o">.</span><span class="n">Configuration</span><span class="p">()</span>
 
 <span class="c"># Get the extra SIP flags needed by the imported PyTQt modules.  Note that</span>
 <span class="c"># this normally only includes those flags (-x and -t) that relate to SIP&#39;s</span>
 <span class="c"># versioning system.</span>
-<span class="n">pyqt_sip_flags</span> <span class="o">=</span> <span class="n">config</span><span class="o">.</span><span class="n">pyqt_sip_flags</span>
+<span class="n">pytqt_sip_flags</span> <span class="o">=</span> <span class="n">config</span><span class="o">.</span><span class="n">pytqt_sip_flags</span>
 
-<span class="c"># Run SIP to generate the code.  Note that we tell SIP where to find the qt</span>
+<span class="c"># Run SIP to generate the code.  Note that we tell SIP where to find the tqt</span>
 <span class="c"># module&#39;s specification files using the -I flag.</span>
-<span class="n">os</span><span class="o">.</span><span class="n">system</span><span class="p">(</span><span class="s">&quot; &quot;</span><span class="o">.</span><span class="n">join</span><span class="p">([</span><span class="n">config</span><span class="o">.</span><span class="n">sip_bin</span><span class="p">,</span> <span class="s">&quot;-c&quot;</span><span class="p">,</span> <span class="s">&quot;.&quot;</span><span class="p">,</span> <span class="s">&quot;-b&quot;</span><span class="p">,</span> <span class="n">build_file</span><span class="p">,</span> <span class="s">&quot;-I&quot;</span><span class="p">,</span> <span class="n">config</span><span class="o">.</span><span class="n">pyqt_sip_dir</span><span class="p">,</span> <span class="n">pyqt_sip_flags</span><span class="p">,</span> <span class="s">&quot;hello.sip&quot;</span><span class="p">]))</span>
+<span class="n">os</span><span class="o">.</span><span class="n">system</span><span class="p">(</span><span class="s">&quot; &quot;</span><span class="o">.</span><span class="n">join</span><span class="p">([</span><span class="n">config</span><span class="o">.</span><span class="n">sip_bin</span><span class="p">,</span> <span class="s">&quot;-c&quot;</span><span class="p">,</span> <span class="s">&quot;.&quot;</span><span class="p">,</span> <span class="s">&quot;-b&quot;</span><span class="p">,</span> <span class="n">build_file</span><span class="p">,</span> <span class="s">&quot;-I&quot;</span><span class="p">,</span> <span class="n">config</span><span class="o">.</span><span class="n">pytqt_sip_dir</span><span class="p">,</span> <span class="n">pytqt_sip_flags</span><span class="p">,</span> <span class="s">&quot;hello.sip&quot;</span><span class="p">]))</span>
 
 <span class="c"># We are going to install the SIP specification file for this module and</span>
 <span class="c"># its configuration module.</span>
@@ -382,9 +382,9 @@ life easier for them.</p>
 <span class="n">installs</span><span class="o">.</span><span class="n">append</span><span class="p">([</span><span class="s">&quot;helloconfig.py&quot;</span><span class="p">,</span> <span class="n">config</span><span class="o">.</span><span class="n">default_mod_dir</span><span class="p">])</span>
 
 <span class="c"># Create the Makefile.  The TQtGuiModuleMakefile class provided by the</span>
-<span class="c"># pyqtconfig module takes care of all the extra preprocessor, compiler and</span>
+<span class="c"># pytqtconfig module takes care of all the extra preprocessor, compiler and</span>
 <span class="c"># linker flags needed by the TQt library.</span>
-<span class="n">makefile</span> <span class="o">=</span> <span class="n">pyqtconfig</span><span class="o">.</span><span class="n">TQtGuiModuleMakefile</span><span class="p">(</span>
+<span class="n">makefile</span> <span class="o">=</span> <span class="n">pytqtconfig</span><span class="o">.</span><span class="n">TQtGuiModuleMakefile</span><span class="p">(</span>
     <span class="n">configuration</span><span class="o">=</span><span class="n">config</span><span class="p">,</span>
     <span class="n">build_file</span><span class="o">=</span><span class="n">build_file</span><span class="p">,</span>
     <span class="n">installs</span><span class="o">=</span><span class="n">installs</span>
@@ -407,10 +407,10 @@ life easier for them.</p>
     <span class="s">&quot;hello_sip_dir&quot;</span><span class="p">:</span>    <span class="n">config</span><span class="o">.</span><span class="n">default_sip_dir</span><span class="p">,</span>
 
     <span class="c"># Publish the set of SIP flags needed by this module.  As these are the</span>
-    <span class="c"># same flags needed by the qt module we could leave it out, but this</span>
+    <span class="c"># same flags needed by the tqt module we could leave it out, but this</span>
     <span class="c"># allows us to change the flags at a later date without breaking</span>
     <span class="c"># scripts that import the configuration module.</span>
-    <span class="s">&quot;hello_sip_flags&quot;</span><span class="p">:</span>  <span class="n">pyqt_sip_flags</span>
+    <span class="s">&quot;hello_sip_flags&quot;</span><span class="p">:</span>  <span class="n">pytqt_sip_flags</span>
 <span class="p">}</span>
 
 <span class="c"># This creates the helloconfig.py module from the helloconfig.py.in</span>
@@ -419,14 +419,14 @@ life easier for them.</p>
 </pre></div>
 </div>
 <p>Next we have the <tt class="docutils literal"><span class="pre">helloconfig.py.in</span></tt> template script:</p>
-<div class="highlight-python"><div class="highlight"><pre><span class="kn">from</span> <span class="nn">PyTQt4</span> <span class="kn">import</span> <span class="n">pyqtconfig</span>
+<div class="highlight-python"><div class="highlight"><pre><span class="kn">from</span> <span class="nn">PyTQt4</span> <span class="kn">import</span> <span class="n">pytqtconfig</span>
 
 <span class="c"># These are installation specific values created when Hello was configured.</span>
 <span class="c"># The following line will be replaced when this template is used to create</span>
 <span class="c"># the final configuration module.</span>
 <span class="c"># @SIP_CONFIGURATION@</span>
 
-<span class="k">class</span> <span class="nc">Configuration</span><span class="p">(</span><span class="n">pyqtconfig</span><span class="o">.</span><span class="n">Configuration</span><span class="p">):</span>
+<span class="k">class</span> <span class="nc">Configuration</span><span class="p">(</span><span class="n">pytqtconfig</span><span class="o">.</span><span class="n">Configuration</span><span class="p">):</span>
     <span class="sd">&quot;&quot;&quot;The class that represents Hello configuration values.</span>
 <span class="sd">    &quot;&quot;&quot;</span>
     <span class="k">def</span> <span class="nf">__init__</span><span class="p">(</span><span class="bp">self</span><span class="p">,</span> <span class="n">sub_cfg</span><span class="o">=</span><span class="bp">None</span><span class="p">):</span>
@@ -444,9 +444,9 @@ life easier for them.</p>
 
         <span class="n">cfg</span><span class="o">.</span><span class="n">append</span><span class="p">(</span><span class="n">_pkg_config</span><span class="p">)</span>
 
-        <span class="n">pyqtconfig</span><span class="o">.</span><span class="n">Configuration</span><span class="o">.</span><span class="n">__init__</span><span class="p">(</span><span class="bp">self</span><span class="p">,</span> <span class="n">cfg</span><span class="p">)</span>
+        <span class="n">pytqtconfig</span><span class="o">.</span><span class="n">Configuration</span><span class="o">.</span><span class="n">__init__</span><span class="p">(</span><span class="bp">self</span><span class="p">,</span> <span class="n">cfg</span><span class="p">)</span>
 
-<span class="k">class</span> <span class="nc">HelloModuleMakefile</span><span class="p">(</span><span class="n">pyqtconfig</span><span class="o">.</span><span class="n">TQtGuiModuleMakefile</span><span class="p">):</span>
+<span class="k">class</span> <span class="nc">HelloModuleMakefile</span><span class="p">(</span><span class="n">pytqtconfig</span><span class="o">.</span><span class="n">TQtGuiModuleMakefile</span><span class="p">):</span>
     <span class="sd">&quot;&quot;&quot;The Makefile class for modules that %Import hello.</span>
 <span class="sd">    &quot;&quot;&quot;</span>
     <span class="k">def</span> <span class="nf">finalise</span><span class="p">(</span><span class="bp">self</span><span class="p">):</span>
@@ -456,7 +456,7 @@ life easier for them.</p>
         <span class="bp">self</span><span class="o">.</span><span class="n">extra_libs</span><span class="o">.</span><span class="n">append</span><span class="p">(</span><span class="s">&quot;hello&quot;</span><span class="p">)</span>
 
         <span class="c"># Let the super-class do what it needs to.</span>
-        <span class="n">pyqtconfig</span><span class="o">.</span><span class="n">TQtGuiModuleMakefile</span><span class="o">.</span><span class="n">finalise</span><span class="p">(</span><span class="bp">self</span><span class="p">)</span>
+        <span class="n">pytqtconfig</span><span class="o">.</span><span class="n">TQtGuiModuleMakefile</span><span class="o">.</span><span class="n">finalise</span><span class="p">(</span><span class="bp">self</span><span class="p">)</span>
 </pre></div>
 </div>
 <p>Again, we hope that the scripts are self documenting.</p>