-On [20071120 16:17], Christian Boos ([EMAIL PROTECTED]) wrote: >Getting to the constructor call style for raising TracError (and other >exceptions) was a gradual process, and it might well be that there are >still (a few) old-style raise statement. You're welcomed to fix those, >but as usual for the i18n branch, please consider making any non-i18n >infrastructure related change on trunk /first/, as to avoid possible >merge issues.
That's why I raised the issue on the list first, didn't want to get in the way of any on-going work. I guess Manu is going to fix this, judging from the other email, if not Manu, I'll gladly do it. Just let me know. >Btw, how went that last little merge? ;-) Only main.py in web/ was a bit more work, otherwise almost no issues. -- Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ | http://www.rangaku.org/ Tonight your soul sleeps, but one day you will feel real pain, maybe then you will see me as I am: a fragile wreck on a storm of emotion... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
