On 1.6 now. I think we used a pre-release 1.5 version for a while with Python 3 as well. I tried getting my plugins ported before 1.6 came out.
Yes, the loss of Genshi is the real problem, it seems to me. I did a couple conversions for that. - Dan On Monday, December 15, 2025 at 11:28:58 AM UTC-6 ichthyo wrote: > On 15/12/2025 17:38, Dan wrote: > > I'm not sure if I can help out a lot with this, but FYI my group is > using child > > tickets plugin. It does check for open child tickets and prevent > closing the > > parent if so. > > Thanks, good to know. At least someone is using it... > > > Yes, we've been using Python 3 version for for quite a few years. > > Which version of Trac are you on? > > > I ported a few plugins myself, but it's been a while lol ... > > Indeed, the porting to python-3 is usually not that hard, > in most cases it boils down to turning "print" into a function > and then to figure out where generators are used, because these > do not return a list any more. > > But with Trac there is also the twist with the move away from > the Genshi templating engine, which allowed for post-processing. > If a plugin relied on that in a substantial way(as mastertickets did), > then just porting is not enough, it would require a complete rewrite. > > Thanks anyway for your answer, very much appreciated > > -- Hermann > > > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/trac-users/e038914b-9d05-4633-a498-30ba0f509120n%40googlegroups.com.
