Commits

Steven Knight  committed 68aeb24

Delete references to QMTest/unittest.py, which has been removed.

  • Participants
  • Parent commits fa0aca5

Comments (0)

Files changed (3)

File QMTest/SConscript

     'TestSCons.py',
     'TestSConsign.py',
     'TestSCons_time.py',
-    'unittest.py',
 ]
 
 def copy(target, source, env):
         # Run setup.py in the unpacked subdirectory to "install" everything
         # into our build/test subdirectory.  The runtest.py script will set
         # PYTHONPATH so that the tests only look under build/test-{package},
-        # and under etc (for the testing modules TestCmd.py, TestSCons.py,
-        # and unittest.py).  This makes sure that our tests pass with what
+        # and under QMTest (for the testing modules TestCmd.py, TestSCons.py,
+        # etc.).  This makes sure that our tests pass with what
         # we really packaged, not because of something hanging around in
         # the development directory.
         #
         # Run setup.py in the unpacked subdirectory to "install" everything
         # into our build/test subdirectory.  The runtest.py script will set
         # PYTHONPATH so that the tests only look under build/test-{package},
-        # and under etc (for the testing modules TestCmd.py, TestSCons.py,
-        # and unittest.py).  This makes sure that our tests pass with what
+        # and under QMTest (for the testing modules TestCmd.py, TestSCons.py,
+        # etc.).  This makes sure that our tests pass with what
         # we really packaged, not because of something hanging around in
         # the development directory.
         #
             # Run setup.py in the unpacked subdirectory to "install" everything
             # into our build/test subdirectory.  The runtest.py script will set
             # PYTHONPATH so that the tests only look under build/test-{package},
-            # and under etc (for the testing modules TestCmd.py, TestSCons.py,
-            # and unittest.py).  This makes sure that our tests pass with what
-            # we really packaged, not because of something hanging around in
-            # the development directory.
+            # and under QMTest (for the testing modules TestCmd.py,
+            # TestSCons.py, etc.).  This makes sure that our tests pass with
+            # what we really packaged, not because of something hanging around
+            # in the development directory.
             #
             # We can get away with calling setup.py using a directory path
             # like this because we put a preamble in it that will chdir()
             # Run setup.py in the unpacked subdirectory to "install" everything
             # into our build/test subdirectory.  The runtest.py script will set
             # PYTHONPATH so that the tests only look under build/test-{package},
-            # and under etc (for the testing modules TestCmd.py, TestSCons.py,
-            # and unittest.py).  This makes sure that our tests pass with what
-            # we really packaged, not because of something hanging around in
-            # the development directory.
+            # and under QMTest (for the testing modules TestCmd.py,
+            # TestSCons.py, etc.).  This makes sure that our tests pass with
+            # what we really packaged, not because of something hanging
+            # around in the development directory.
             #
             # We can get away with calling setup.py using a directory path
             # like this because we put a preamble in it that will chdir()

File src/test_strings.py

             'QMTest/configuration',
             'QMTest/TestCmd.py',
             'QMTest/TestCommon.py',
-            'QMTest/unittest.py',
             'src/os_spawnv_fix.diff',
             'src/MANIFEST.in',
             'src/setup.cfg',