Quoting Remy Blank <[EMAIL PROTECTED]>: > You'll see that one of the ticket has a NULL value as the milestone. > Whether these two values should be treated differently is debatable, though.
Indeed, now I see the difference: 1||new 2|NULL|new Maybe it would be wise, if trac would leave an unset milestone field completely empty in the reports, no matter whether this is internally stored as a NULL value or as an empty string. (Or component or version.) "None" might look like "something" to the non-Pythonist. This works for me: --- report.py.orig 2008-11-14 13:25:14.000000000 +0100 +++ report.py 2008-11-14 13:32:55.000000000 +0100 @@ -406,7 +406,10 @@ for header_group in header_groups: cell_group = [] for header in header_group: - value = unicode(result[col_idx]) + if result[col_idx]: + value = unicode(result[col_idx]) + else: + value = "" cell = {'value': value, 'header': header, 'index': col_idx} col = header['col'] col_idx += 1 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---