P4DTI issue job000139

TitleTrigger scripts duplicate replicator code
Assigned userRichard Brooksby
DescriptionThe example trigger script we provide has its own interface to Perforce, duplicating the "p4" class in the replicator. It would be better to share the code, for maintainability and robustness.
AnalysisThe big question is how we'd find the p4 class. Should it be perhaps installed as a Python library, on the system path, or in "site-python" or the equivalent place? I'm leaving it alone for the moment as we don't have a good answer. RB 2000-12-06
GDR 2001-07-17: We should have a standalone p4.py that people could install and use; contribute to python.org etc etc. The one in code/replicator is not so good for this because it uses our logging, message, catalog stuff and checks for particular Perforce versions. Might want more methods.
How foundinspection
EvidenceNoticed myself copying and pasting code when I was writing it. RB 2000-12-06
Observed in0.4.0
Introduced in0.4.0
Created byRichard Brooksby
Created on2000-12-07 12:04:52
Last modified byRichard Brooksby
Last modified on2013-03-15 12:19:47
History2000-12-06 RB Created.
2013-03-15 RB Suspended ancient job in defunct project.