|
[Rivet] [Rivet-svn] r1745 - in trunk: include/Rivet srcFrank Siegert frank.siegert at durham.ac.ukWed Aug 5 17:36:29 BST 2009
Frank Siegert, Wednesday 05 August 2009: > blackhole at projects.hepforge.org, Wednesday 05 August 2009: > > Author: fsiegert > > Date: Wed Aug 5 16:34:46 2009 > > New Revision: 1745 > > Nevermind. On a different machine the problem is still there, even > without the smart pointer. So I'll debug further ... It seems that I have to remove the pre-created rivet.py* and rivet_wrap.cc* from the pyext directory and have them recompiled. Otherwise all kinds of undeterministic things happen, e.g. the second point in https://projects.hepforge.org/rivet/trac/ticket/323 was solved by this in the case which I have just tested. Now this seems to be a generic problem that the Python interface will have to be updated when the classes change. Maybe it would already help, if the functions are not implemented in the header file, but in the source? Then at least changes in them wouldn't affect the Python interface files. Or am I completely wrong? If nobody objects I can do that. Andy, could you then afterwards recreate the rivet.py-HepMC* and rivet_wrap.cc-HepMC* files such that they are up- to-date with the classes? Frank
More information about the Rivet mailing list |