On 06/04/2010 03:53 AM, Manuel Jes?s Recena Soto wrote: > Hi, again. > > Can someone help me? > maybe I should send this message to another list?
I think no one has responded because the possible fixes are fairly evident, given all of your initial analysis. (1) Fix the code (2) Use python 2.6 For what it's worth, both at work and at home, I maintain a separate git repository of Trac code (both core and trac hacks) pulled from the source upstream repositories to which I apply fixes and changes. Many of these changes come from patches in open tickets. In fact, I'd be surprised if anyone runs the core trac code with no personal source modifications.. it's just too darn hackable to leave alone. ;-) -- SIXNET - Industrial and Wireless Connectivity 331 Ushers Road, Ballston Lake, NY 12019 Tel: 1.518.877.5173, Fax: 1.518.877.8346 www.sixnet.com -- You received this message because you are subscribed to the Google Groups "Trac Users" 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-users?hl=en.
