##// END OF EJS Templates
transaction: issue "new obsmarkers" message at the end of the transaction...
transaction: issue "new obsmarkers" message at the end of the transaction Instead of making bundle2 code responsible for this, it seems better to have it handled and the transaction level. First, it means the message will be more consistently printed. Second it means we won't spam the message over and over if the data arrive in multiple piece. Third, we are planning to move other similar message at the same level (for the same reason) so having them all at the same location will help us to control the order they are displayed.

File last commit:

r30477:d2c40510 default
r43164:38392d5b default
Show More
sitecustomize.py
16 lines | 466 B | text/x-python | PythonLexer
Robert Stanca
py3: use absolute_import in sitecustomize.py
r28946 from __future__ import absolute_import
Gregory Szorc
run-tests: collect aggregate code coverage...
r24505 import os
if os.environ.get('COVERAGE_PROCESS_START'):
try:
import coverage
Augie Fackler
tests: update sitecustomize to use uuid1() instead of randrange()...
r30477 import uuid
Gregory Szorc
run-tests: collect aggregate code coverage...
r24505
covpath = os.path.join(os.environ['COVERAGE_DIR'],
Augie Fackler
tests: update sitecustomize to use uuid1() instead of randrange()...
r30477 'cov.%s' % uuid.uuid1())
Gregory Szorc
run-tests: collect aggregate code coverage...
r24505 cov = coverage.coverage(data_file=covpath, auto_data=True)
cov._warn_no_data = False
cov._warn_unimported_source = False
cov.start()
except ImportError:
pass