Avoid spurious object copy in range for.

Avoid spurious object copy in range for.

Work around an issue seen with cling 6.20.06.
If classes are created in the wrong order, cling can get confused
with forward declarations.  This happens with a test in this package.
Explicitly force the pythonization of a class at the appropriate
time to avoid this.

Name of one TileCal cell monitoring histogram has been corrected
to be compatible with Run2.

 - Prefer preincrement to postincrement for user iterators.
 - Prohibit copying for some test classes.
 - Iterator fix.
 

 - Pass large structures by const reference rather than by value.
 

 - Prefer preincrement rather than postincrement for user iterators.
 - assert with side effects.
 

Format string type mismatch.

 - Issues with assertions with possible side effects.
 - Redundant comparison.
 - Prefer to initialize members in an initialization clause rather than
   a constructor body.
   

Update ICellWeightTool and IHadronicCalibrationTool to use
DeclareInterfaceID.

Migrate H1WeightToolCSC12Generic from ToolWithConstantsMixin
to ToolWithConstants.

Add ToolConstantsCondAlg.
This can convert from COOL inline data to a ToolConstants object
in the conditions store, or alternatively copy a ToolConstants
object from the detector store to the conditions store.

SealSvc does not have any useful function any more

Small fix for python 3 compatibility.

    
Don't declare conditions dependencies that we don't use.

Don't declare conditions dependencies that we don't use.

Change CaloClusterCorrDumper so that instead of using ToolWithConstantsMixin
(which is going away), it dumps ToolConstants objects directly
from the conditions store.

More fixes for python 3 compatibility.

More fixes for python 3 compatibility.

Migrate LArMinBiasAlg from the obsolete LArMCSymTool to the
LArMCSym conditions object.

Needed to avoid warings from the thread-safety checker.

Increase timout for test that has been timing out in dbg builds.

Fix typos in previous change.

Switch the cluster correction classes from ToolWithConstantsMixin
to ToolWithConstants.

The metatool (CaloRunClusterCorrections) does not yet work with the new
class, so it has been disabled.   This implies that one cannot configure
the list of corrections from only a cool tag.  In many cases, though,
the cool tag had already been replaced by a static version.
For now, adjust the configuration so that we always use a static
configuration, rather than the tag.  This should be revisited later.

The configuration scripts also need some further cleanup, to be done
in a future change.

CaloCellContainerCheckerTool: Move retrieval of CaloCell_ID to initialize() to work around rare threading problem

The generic way to retrieve a constant in ToolWithConstants is to call
operator() on it, passing in a Context object.  Added another operator()
which does not take arguments.  This can be used only if the constant
has been initialized from job options.  (The intended use case is for
the L2 trigger.)

Need to flush output to get consistent output ordering
between py2 and py3.