- attached tupleformatting.patch
Outputting "Unicde type received non-uniode bind" warning raises exception for tuples
Issue #1854
resolved
the following code appears in a few places where value can be a tuple and thus confuse the string formatting:
This should be corrected to:
{{{"param value %r" % (value,)}}}
I don't know if this is present in 0.6: At first glance the code in question appears to have moved and been rewritten.
Comments (4)
-
Account Deleted -
repo owner - changed milestone to 0.5.9
that code is all obsolete, yes, and technically you're not supposed to be passing in tuples to string cols, but its true the error message shouldn't fail. It's unlikely at the moment that we're doing any more 0.5 releases, though, its better if people upgrade to 0.6.
If we were to patch 0.5 I think it would be better to take the approach of
#1822, since embedding ad-hoc strings in warnings apparently causes an arbitrarily large list of strings to be stowed away in the warnings module. -
repo owner - changed status to wontfix
this patch is good though obsolete as there are no 0.5 releases planned
-
repo owner - removed milestone
Removing milestone: 0.5.9 (automated comment)
- Log in to comment
Patch against rel_0_5 to fix this