To bring the discussion back to crank, and relate to what Chris said. Crank actually allows us to move over to pyramid without maintaining multiple codebases if we decide to do that. I realize we are spinning off one of the major parts of TG, but I think in this case it makes sense. This was a big problem with TG1.0, 1.5 and 2.0, all of which have separate codebases to maintain for dispatch.
I agree that TG should remain as a first-class citizen with Crank, and that backwards compatibility should be maintained. I have done everything in my power to make sure that the existing 2.1.x tests work with crank in the codebase. As a side note, I'm writing something to remove the repoze.w* mess, and I plan on spinning off the part of the code that selects templates/template engines into it's own package, or partnering with Alice of web.core to utilize alacarte, which is a replacement for buffet. I'm tired of maintaining multiple dotted template lookup code too ;-) cheers. -chris -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To view this discussion on the web visit https://groups.google.com/d/msg/turbogears-trunk/-/7F_CCpa9aZgJ. 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-trunk?hl=en.
