On Jan 10, 2008 7:32 AM, Justin <[EMAIL PROTECTED]> wrote: > > Greetings, > > I've got some projects coming up that I'm currently planing to develop > using Pylons. I follow this mailling list and it seems there are some > pretty big framework changes coming to 0.9.7. Do the developers > recommend working with the current trunk code or sticking with the > release version and then updating later? Is there a current time-frame > for 0.9.7s release?
0.9.7 is scheduled for March, hopefully before PyCon. I've been nudging Ben to release an alpha because part of the work has been done. At this point it's a toss-up whether to use 0.9.6.1 or dev for an app to be released in the six-week-or-longer timeframe. The changes to Pylons core are mostly housekeeping and don't affect application code much. They have been stable for a few weeks, and tested on my application at least. Keep an eye on "What's New in Pylons 0.9.7" for an explanation of committed changes, and "Pylons Roadmap to 1.0" for future plans. http://wiki.pylonshq.com/pages/viewpage.action?pageId=11174779 http://wiki.pylonshq.com/display/pylonscommunity/Pylons+Roadmap+to+1.0 Currently if you create a project in dev, it will: - Add the three new required middlewares in middleware.py. (For routing, sessions, and error handling.) [To make the app compatible with both dev and 0.9.6, put an "if" around these as described in What's New.] - Ask if you want SQLAlchemy and if so, set up the latest & greatest configuration in model,py, environment,py, and development.ini. [Should work under 0.9.6 as is.] - Add "use_webob=False" in middleware.py. If you set this to true, it will use webob.Request and webob.Response, which are more complete and better documented than the older objects. Docs at http://pythonpaste.org/webob. At some point, WebOb will be required. [For 0.9.6 compatibility, use an "if" to avoid mentioning "use_webob" in the older version. Also put an "if" around each access to a WebOb attribute/method, to fall back to the equivalent older method. The most common usage, request.params, is unchanged.] The most disruptive changes will be in Routes, WebHelpers, and templating. but those are still vaporware so it doesn't matter which version of Pylons you target at this time. I'm trying to announce potential changes early so users can anticipate them and isolate those portions of their code. Pylons-dev currently depends on Routes 1.7.1, which is stable and compatible. Don't use Routes-dev because it has a serious bug (url_for sometimes returns None), and that development branch will be abandoned. Routes 2 will have a different configuration syntax and url_for syntax, but you'll probably be able to use either Routes 2 or Routes 1 with 0.9.7 if you're happy with your existing routes. The main reason to switch to Routes 2 is it will be simpler and more deterministic, making it easier to predict which route will be chosen. WebHelpers changes are totally up in the air, so just use the existing functions for now. Template changes will be limited to the configuration in environment.py, and the render() arguments. I'm not sure if it there will be incompatible changes or not. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
