I've been working on CherryPy 3.1 support (ticket #1181) lately, and have made good progress -- to the point where it would benefit from having another set of eyes.
In brief, all the core tests, i18n, & all but one of the widget tests pass. Freshly quickstarted applications run fine. Visit (& thus identity) are currently broken, (I haven't figured out how to convert MonkeyDecodingFilter to a tool yet) and I know of some features that aren't currently tested & need a closer look (VirtualPath, object_trail, fancy_exception, BonJour). Otherwise, I believe the changes to be pretty clean. I'd like to make a cp31 branch & start committing to it. Any objections? I'd rather not just attach a diff to the ticket for review, since: (a) it would be pretty sizable & hard to read as one big change, (b) the fact that the changes are based on the work of others would be lost (I started with the old cp3 branch as a basis), and (c) I'm hoping that someone might be interested in joining the fun. While the list of remaining issues isn't huge, there are enough items that would be a pain to pass back & forth through a ticket. Also, is anyone interested in helping work out the remaining kinks? There's a lot of goodness [1] to be had.. -Ken [1] http://www.cherrypy.org/wiki/WhatsNewIn30, http://www.cherrypy.org/wiki/WhatsNewIn31, http://www.cherrypy.org/wiki/PageHandlers --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
