Thanks Russ! >>> My only question is whether overriding __str__ is the right >>> place; given that as_string() is the affected interface, it seem like >>> that should be the method that is fixed.
It looks like you're right. as_string() is the right method to override. I'll put a patch together. > I'm sure this particular bug is annoying in your > particular case, but there are plenty of annoying edge case bugs in > Trac that are annoying to various people. Unfortunately, if we're > *ever* going to release 1.2, we need to draw the line somewhere. No worries, I just figured it couldn't hurt to ask. > However, if you get a patch worked up, this could be a very early > commit in the 1.3 timeframe. I'll put a patch together, but I'd happily trade the 'get an early commit into 1.3' card in for http://code.djangoproject.com/ticket/11716 - IMO that one's a much bigger deal :-) -- --Leo -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
