PythonModule.cc

Go to the documentation of this file.

#ifndef FWCore_PythonFramework_PythonModule_h
#define FWCore_PythonFramework_PythonModule_h

#include "FWCore/PythonParameterSet/interface/BoostPython.h"
#include "FWCore/PythonParameterSet/interface/PythonProcessDesc.h"

#include "FWCore/PythonFramework/interface/PythonEventProcessor.h"
#include "FWCore/Utilities/interface/Exception.h"

// This is to give some special handling to cms::Exceptions thrown
// in C++ code called by python. Only at the very top level do
// we need the exception message returned by the function "what".
// We only need the central message here as this will get converted
// back into a cms::Exception again when control rises back into
// the C++ code.  If necessary it would probably be possible to
// improve these messages even more by adding something in the python
// to add module type and label context to the messages being caught
// here. At this point we did not think it worth the time to implement.
namespace {
  void translator(cms::Exception const& ex) {
    PyErr_SetString(PyExc_RuntimeError, ex.message().c_str());
  }
}

BOOST_PYTHON_MODULE(libFWCorePythonFramework)
{
  boost::python::register_exception_translator<cms::Exception>(translator);

  boost::python::class_<PythonEventProcessor, boost::noncopyable>("PythonEventProcessor", boost::python::init<PythonProcessDesc const&>())
    .def("run", &PythonEventProcessor::run)
    .def("totalEvents", &PythonEventProcessor::totalEvents)
    .def("totalEventsPassed", &PythonEventProcessor::totalEventsPassed)
    .def("totalEventsFailed", &PythonEventProcessor::totalEventsFailed)
  ;
}
#endif