as the 20th century poet ozzy osbourne once written: "let it go, let it die."
On Wednesday, February 18, 2015 at 11:15:29 AM UTC+2, [email protected] wrote: > > I'm writing here because I'm fearing we will have to make a clear step > regarding genshi in the near future. So I would like to gather as much > opinions as possible regarding the matter. > > Currently we have a major issue with TurboGears on Python3.4 caused by > Genshi not working there due to changes into the ast module. The issue has > actually been already patched nearly and year ago in genshi itself, but no > new releases ever happened. > > I have been able to provide a genshi.name_constant_patch option in TG > genshi renderer that monkeypatches it to make it work on Py3.4, but this is > actually a temporary work-around and is far from being an acceptable > solution. > > I also got in touch with Simon Cross half an year ago and he confirmed he > was willing to make a new genshi release, but it still didn't happen. > > Any suggestion on how to proceed? > I'm currently only able to think of replacing Genshi with Kajiki as the > official TG template engine in a future major release. I'm unable to > maintain genshi itself as its codebase is quite complex and hard to > maintain, while Kajiki is 90% compatible with genshi while having a much > simpler codebase and faster performances. > > This is off course a last resort and I would really like to avoid having > to proceed that way, but if Genshi is not maintained anymore and it stops > working on future python releases I'm currently unable to see a better move > :/ > -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/d/optout.
