issue2551107 - Handle long int in history params

Early versions of roundup represented the id in a params tuple of the
journal/history using a Long int. The repr 2345L is not valid under
python3. So eval()'ing the params tuple throws a SyntaxError. Trap the
error, modify the parms string stripping the L and re-eval.

Author: rouilj

CHANGES.txt

@@ -41,6 +41,12 @@ Fixed:
 - REST replace hard coded list of child endpoints for /rest/ with list
   pulled from registered endpoints. So newly added endpoints are
   shown. (John Rouillard)
+- issue2551107 - Handle representation of long int in history params
+  for python3. Causes SyntaxError crash when showing history due to
+  long int e.g. 2345L. This is not a problem for roundup trackers
+  created using 1.2.0 or newer. The fix may have predated the 1.2.0
+  release but where the fix actually landed (representing id as a
+  string and not as an int) is unknown.
 
 Features:
 

roundup/anypy/strings.py

@@ -142,7 +142,15 @@ def repr_export(v):
 def eval_import(s):
     """Evaluate a Python-2-style value imported from a CSV file."""
     if _py3:
-        v = eval(s)
+        try:
+            v = eval(s)
+        except SyntaxError:
+            # handle case where link operation reports id a long int
+            # ('issue', 5002L, "status") rather than as a string.
+            # This was a bug that existed and was fixed before or with v1.2.0
+            import re
+            v = eval(re.sub(r', ([0-9]+)L,',r', \1,', s))
+
         if isinstance(v, str):
             return v.encode('iso-8859-1').decode('utf-8')
         elif isinstance(v, dict):