Hi, everyone! PyCon was definitely a good time. I highly recommend it to folks. It was a great chance to meet many people doing a wide variety of things with Python. The talks covered a fair number of topics (including a sneak preview of Python 2.5 for those of us not watching python-dev).
We had a good turnout for the sprint. On Sunday, we did some planning on what we would do and how we'd proceed. There were about 12 of us! We were split into 3 teams, working on Docudo, Kid and TurboGears WSGI. Joel Pearson sent me a Docudo update last night saying that they've got a spec together and Docudo is now like a "wiki20" plus: stores in subversion, edits pages using TinyMCE and keeps pages in separate project version namespaces. For those new to Docudo: the idea is to create a web-based tool that fixes some of the warts of using a wiki for software project documentation. You can join in on Docudo! The mailing list is here: http://groups.google.com/group/docudo and the Subversion repository is here: http://www.turbogears.org/svn/docudo In addition to Joel, Karl Guertin, Mike Orr, Arthur McLean, Kevin Horn all participated in Docudo. Mike Pirnat and David Stanek were working on Kid. They created tests that time a variety of Kid's operations and squeezed out some performance gains. Then they embarked on a major restructuring of Kid's internals with an aim to simplify. Kid jumps through some hoops to stream documents and can become much simpler if those hoops aren't there. I left before they did yesterday, so I'm not certain where they left off. I was working with Ian Bicking, Gary Godfrey, Matt Good and Bill Zingler on better WSGI support for a future TurboGears version. This is in the tgpycon branch that was apparently scaring some folks on Monday. That branch doesn't pass all of the original tests yet, but it does pass some new and interesting ones. As of now, you can instantiate a TurboGears application right in your object tree and have URL and configuration sanity. You can also attach a TurboGears app to a URL via a config file. And mix a TurboGears app with other WSGI apps that are possibly written with other frameworks. Before I left yesterday, Gary Godfrey told me about his next step with that branch and his change was going to make it even more flexible and useful by making each controller class a "WSGI app" with the ability to insert "middleware" at any part of your stack. You'll also have incredible control over how object traversal wants *if you want to*. This branch has a goal that existing TurboGears apps should continue working without modifications. We're well on the way with that goal, but serious testing will be needed. My plan for this branch is that after 0.9 enters beta, I'll branch 0.9. The tgpycon branch will then move to the trunk to get more serious attention. That code won't be out until after TG 1.0, though. We got some real traction on some "big ticket items", which I'm very pleased about. These would have been much harder to work out individually and I think we've got enough started that we'll be able to keep the work going and get contributions from others now that the sprint is over. Feel free to try out the tgpycon branch and talk about it on the list. Kevin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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 -~----------~----~----~----~------~----~------~--~---
