[p4python] p4 diff2 vs. run_diff2

Robert Cowham robert at vaccaperna.co.uk
Mon Dec 12 08:46:05 PST 2005

I think this is an oddity of the API. I will investigate when I get some
time as to where the output goes if you call parse_forms().

I wonder what difference tagged() makes instead of parse_forms()?

You certainly shouldn't be using diff instead.

Meanwhile, the work around is to not use parse_forms() and just parse the
output - sorry about that.


> -----Original Message-----
> From: p4python-bounces at perforce.com 
> [mailto:p4python-bounces at perforce.com] On Behalf Of Nicholas 
> Guarracino
> Sent: 09 December 2005 22:26
> To: p4python at perforce.com
> Subject: [p4python] p4 diff2 vs. run_diff2
> I'm trying to see what's changed in a particular file using 
> diff2. On the command line I can run
> p4 -dc //depot/file at filerev1 //depot/file at filerev2
> And it shows me the diff, just as expected. Going through the 
> python API gives me a dictionary with keys 'status', 
> 'depotFile', etc. However, nowhere do I see the actual output 
> of the diff2 command. What I discovered is that if I don't 
> run parse_forms() at the start of my script, run_diff2 does 
> return the output, albeit in a much less organized fashion. 
> Is there any way to see the actual diff2 output after calling 
> parse_forms()? Should I be using diff instead of diff2?
> Thanks!
> -- 
> Nicholas Guarracino
> DataViz, Inc.
> _______________________________________________
> p4python mailing list
> p4python at maillist.perforce.com
> http://maillist.perforce.com/mailman/listinfo/p4python

More information about the p4python mailing list