Florent Aide wrote: >> And we should also cover this case in the unit tests. > > I have some code on my machine that is still pretty messed-up but > which should cover nearly all the cases... I need to do some more > testing and then I'll ask for some review because I don't have enough > testing material to make sure of every corner by myself.
I have already checked in what I believe to be a complete fix and unit test coverage for this issue, because I urgently needed it for an app in production. Can you have a look at it? If you think it is ok, then can you make a 1.04b4 release since this issue is breaking a lot of apps and people are creating new tickets for this all of the time. Also, I noticed that this whole thing has been handled only in the 1.0 branch so far, and not been merged to the 1.1 branch. Shall I go for it or is there a reason why we don't want/need to have this in 1.1? -- Christoph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
