gracefully handle no-match in p4 info regex
Review Request #3902 — Created Feb. 21, 2013 and submitted — Latest diff uploaded
If the regular expression doesn't parse the string that p4 info returns, calling group will cause a traceback. This came up where p4 info returned an unexpected string.
Manual testing with the p4 binary that returned a non-standard string. I'm on OSX and I'm not going to spend the non-trivial time to get unit tests running. No hard feelings if you reject this patch on that basis.
Diff Revision 1
This is not the most recent revision of the diff. The latest diff is revision 3. See what's changed.
orig
1
2
3
| rbtools/clients/perforce.py |
|---|