>> That is great news! How much work was involved in porting your app and >> which part of it did you need to change most? > > The main work was actually finishing the work on the TG 1.5 branch so > that it would run my old TG 1.1 app with server.webpath etc. properly. > > Since TG 1.5 offers Genshi widget templates now, I used the opportunity > to convert all my page and widget templates to Genshi. This was not a > big deal, and the tgadmin kid2genshi command is helping a lot. > > But TG 1.5 does still support Kid, so you don't even need to do this.
I still use kid, but actually might switch to genshi if you say it's easy with 'tgadmin kid2genshi'. > Upgraded to the latest SQLAlchemy version was not a big deal either, > since TG 1.5 emulates the old session-aware mapper. By the way, does tg 1.5 still support sqlobject? My number one reason for not porting my app to tg2 is that tg2 does not support sqlobject anymore. > Some small changes in the config were necessary. I will write up the > detailed instructions in the TG 1.5 wiki when I find some time. > > A minor problem with CherryPy 3 is that you can't do "from cherrypy > import session" any more since sessions are now only available after > startup. I will add some documentation on how to manually set up the > sessions early, and how to implement a visit based session backend for > CherryPy (the ram sessions have problems with mod_wsgi, the file based > sessions can be problematic, and the Postgres based session would not > use the already existing connection pool used by SQLAlchemy). The former > problem can of course also be solved by simply referencing the session > as cherrypy.session everywhere. I also use the sqlobject specific visit framework from tg1, in case tg1.5 supports sqlobject, does it also support the old visit framework? > One thing I still need to port over is my error catcher code that shows > nicer error pages and sends error reports to the admin. We had a recipe > for TG 1.1 that unforuntately works only with CherryPy 2. I'll need to > create a recipe for CherryPy 3. > > But unless your app relies on CherryPy internals, updating from TG 1.1 > to TG 1.5 is not a big deal. That is good to know, my only worry is so vs sa, as far as I understand your description. Cheers, Daniel -- Psss, psss, put it down! - http://www.cafepress.com/putitdown -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en.
