On Fri, Nov 5, 2010 at 1:50 PM, Jens Hoffrichter <[email protected]> wrote: > - The deprecation of rails-style webhelpers. We depend on those quite a bit > in our first application we wrote (and which is still live)
WebHelpers 0.6.4 is still on PyPI for just this reason. But it was hard to maintain, the APIs were borrowed from Rails without much thought, and the implementations did a lot of naive string concatenation. That was hard to maintain and extend, and if we wanted to jettison it we had to do it before 1.0. > - Change in how to address a template (from "package.template" to > "package/template.mak") Did Pylons ever have this? I think it was only in TurboGears. Maybe it came to Pylons via the first version of Buffet and its Cheetah plugin (horrible). > - The move from implicit routes to explicit routes Another example of a bad early decision in Pylons, and thus the need for a somewhat-painful transition. We're aware that the transitions to 0.9.7 and 1.0 caused frustrations like these. We're trying to minimize that in future versions by keeping Pylons 1 viable for at least a few years after Pyramid is released. But at some point we'll be discouraging writing new applications in Pylons 1. Sometime in the future after Pyramid is released. -- 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.
