@@ -0,0 +1,1249 @@
+# -*- coding: utf-8 -*-%0A%22%22%22sitecustomize %E2%80%95 Handles potential loading of extra code when Python starts.%0A%0A**Module Usage:**%0A%0AThis is normally (this seems not to work with Twisted, for as-of-yet unknown%0Areasons) useful for using :mod:%60coverage%60 to measure code execution in spawned%0Asubprocesses in the following way:%0A%0A 1. Set the environment variable %60%60COVERAGE_PROCESS_START%60%60 to the absolute%0A    path of the coverage config file. If you are in the top-level of the%0A    bridgedb repo, do:%0A%0A        $ export COVERAGE_PROCESS_START=%22$%7BPWD%7D/.coveragerc%22%0A%0A 2. In that coverage config file, in the %60%60%5Brun%5D%60%60 section, set %0A    %60%60parallel = True%60%60.%0A%0A 3. Run coverage. From the top-level of the bridgedb repo, try doing:%0A%0A        $ make reinstall && %5C%0A            coverage run $(which trial) ./lib/bridgedb/test/test_* && %5C%0A            coverage combine && coverage report && coverage html%0A%0AIf %60%60COVERAGE_PROCESS_START%60%60 is not set, this code does nothing,%0A%60%60%5Brun%5D parallel%60%60 should be set to %60%60False%60%60, and coverage can be run by%0Aleaving out the %60%60coverage combine%60%60 portion of the above command.%0A%0ATo view the output HTML coverage data, open%0A%60%60path/to/bridgedb_repo/doc/coverage_html/index.html%60%60 in a browser.%0A%22%22%22%0A%0Aimport coverage%0Acoverage.process_startup()%0A

Add sitecustomize.py for running parallelized coverage tests.