On Fri, Dec 18, 2009 at 4:19 PM, Matt Feifarek <[email protected]> wrote: > First: I SINCERELY hope that I do not start a round of whining, because I am > definitely NOT whining. I am grateful for Pylons and for the support of my > betters in this list. I would ask that any responders to my message NOT use > this as a jumping-off point for whining or bullying, because it is entirely > unwarranted. > Now: > Just wondering, where do the core Devs stand on Pylons 0.10. The > Roadmap/milestone stuff on the PylonsHQ website isn't very informative. I > see some life in the Hg tip, too. > I noticed at the PyCon sprint in Chicago in April that people were very much > talking about 0.10 and 1.0, and there is common talk in this list about how > lots of 0.9.7 is cruft to make backwards compatibility work. > So, if one were *starting* a new legacy-free forward-thinking project, and > was not some "Enterprise" thinking person, should we work on/around Hg tip? > Is there some advantage to not having the cruft in 0.9.7? Is there some > advantage in whatever is different in 0.10 (I realize of course that the > docs won't be accurate). > In short: is it time for a somewhat adventurous sort to switch? > Thanks!
There aren't any significant new features in tip from an application perspective, so there's little reason to use it now unless you want to help with development by running it experimentally and reporting problems. If you plan to put your application in production in the next few months, I'd probably stick with 0.9.7. The "cruft" refers to pre-0.9.7 features which have been deprecated or disrecommended in 0.9.7. If you follow the current Pylons docs and Pylons book, you won' t be using them. They will be deprecated in 0.10 and removed in 1.0. Besides these deprecations, the biggest change in the Changelog is an overhaul of ``cache``, which is being moved under ``app_globals`` and the CacheMiddleware is removed. 'config' is intialized in a slightly different way in environment.py/middleware.py, in order to be friendlier to nested apps. The @validate overhaul has been postponed till after 1.0 because it's too much work. 0.9.7 applications will have to make a few piddly boilerplate changes when they upgrade, similar to the 0.9.6 -> 0.9.7 upgrade. Change 'cache', 'pylons.c' and 'pylons.g' references. Remove CacheMiddleware. Change how 'config' is intialized. Set config['pylons.strict_tmpl_context'] = False if you don't want an AttributeError when reading a nonexistent 'c' attribute in templates. If you start from a devel application template, you can avoid making some of these changes later. But there may be further changes before 0.10/1.0 are released, so you may want to wait and make all the changes at once after the release. Question for Ben: will 'c' and 'g' in templates still be supported? I hope so. -- 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.
