Fixed #10832 -- now use `reorder_suite` in GeoDjango test runner, thanks seanl...

import sys, unittest

from django.test.simple import reorder_suite, TestCase

from django.utils.importlib import import_module

def geo_suite():

    # The test suite.

    s = unittest.TestSuite()

    # Adding the GEOS tests.

    from django.contrib.gis.geos import tests as geos_tests

    s.addTest(geos_tests.suite())

    # Tests that require use of a spatial database (e.g., creation of models)

    test_apps = ['geoapp', 'relatedapp']

        tsuite = import_module('django.contrib.gis.tests.' + suite_name)

        s.addTest(tsuite.suite())

    # Adding the GEOS tests _last_.  Doing this because if suite starts

    # immediately with this test while after running syncdb, it will cause a

    # segmentation fault.  My initial guess is that SpatiaLite is still in

    # critical areas of non thread-safe GEOS code when the test suite is run.

    # TODO: Confirm my reasoning. Are there other consequences?

    from django.contrib.gis.geos import tests as geos_tests

    s.addTest(geos_tests.suite())

    return s, test_apps

def run_gis_tests(test_labels, **kwargs):

        for test in extra_tests:

            suite.addTest(test)

    suite = reorder_suite(suite, (TestCase,))

    # Executing the tests (including the model tests), and destorying the

    # test database after the tests have completed.

    result = unittest.TextTestRunner(verbosity=verbosity).run(suite)