SQLAlchemy and Genshi on TG1.0 or TG2?
Jul 10th, 2008 by diegobz
We’ve been migrating Transifex to use SQLAlchemy, Genshi with i18n support and ToscaWidgets on TG1.0. All seems to work fine until now. That was a part of my GSoC application.
However, continuing implementing new features for Transifex on TG1.0 is not trivial. Specially as we are not using default components like SQLObject, kid template and the own TG1.0 widgets. So, as we already on a big change/migration of components, maybe we could think seriously in a TG2 migration. It could avoid another big change/migration later.
Also, another interesting point for us is implementing too many Ajax features on our tool. That seems to be a promise feature in TG2. Implementing it on the current version of Transifex is not an easy thing to do. To be honest, I don’t know if that worth.
My intend is to follow the tendency, but knowing how much safe it is right now. So…
- How much unstable TG2 is for be used in Trasifex?
- Do we should move to TG2? No? Why not?
- Any thought about Ajax?
Any comment is welcome.
We don’t have TG2 packages for Fedora available yet. As a developer, you still need recognize and be aware of how your application will be deployed. Anything that can’t be deployed via RPM is hell on the Infrastructure team. Having to use easy_install inside a custom python root will make life very difficult indeed.
If you do switch to TG2, I suggest you speak to Luke Macken about helping getting TG2 into Fedora.