make hyperdb value parsing errors readable in mailgw errors

Author: Richard Jones

CHANGES.txt

@@ -21,6 +21,7 @@ Fixed:
 - ensure multilink ordering in RDBMS backends (thanks Marcus Priesch, sf
   bug 950963)
 - always honor indexme property on Strings (sf patch 1063711)
+- make hyperdb value parsing errors readable in mailgw errors
 
 
 2004-10-15 0.7.8

doc/upgrading.txt

@@ -128,6 +128,7 @@ Note that ``tal:`` statements are unaffected. So are TAL expression type
 prefixes such as ``python:`` and ``string:``. Please ask on the
 roundup-users mailing list for help if you're unsure.
 
+
 0.7.0 Edit collision detection
 ------------------------------
 

roundup/mailgw.py

@@ -72,7 +72,7 @@ class node. Any parts of other types are each stored in separate files
 an exception, the original message is bounced back to the sender with the
 explanatory message given in the exception.
 
-$Id: mailgw.py,v 1.149.2.4 2004-10-11 05:20:37 richard Exp $
+$Id: mailgw.py,v 1.149.2.5 2004-11-17 22:10:02 richard Exp $
 """
 __docformat__ = 'restructuredtext'
 
@@ -973,7 +973,7 @@ def setPropArrayFromString(self, cl, propString, nodeid=None):
             props[propname] = hyperdb.rawToHyperdb(self.db, cl, nodeid,
                 propname, value)
         except hyperdb.HyperdbValueError, message:
-            errors.append(message)
+            errors.append(str(message))
     return errors, props