TurboGears joins the Pylons Project
compoundthinking.com
TurboGears joins the Pylons Project
1–10 of 42 posts
Re: TurboGears joins the Pylons Project
#2I was hoping the Pylons blog would have a post about this as well. It's hard to tell what this means for Pylons going forward.
Re: TurboGears joins the Pylons Project
#3[deleted]
Re: TurboGears joins the Pylons Project
#4[deleted]
TG2 is using Pylons 1.0 but for the next major release of Pylons, Pylons merged with repoze.bfg becoming pyramid. Now the word Pylons refer to the project where pyramid is being developed. A little confusing but it's explained here: http://docs.pylonshq.com/
Re: TurboGears joins the Pylons Project
#5A bit unsettling for me. I use Pylons on several projects, though I haven't kept up with Pylons news. I really like Pylons because it was to me the best representation of the ideal framework out there; it was flexible and easy to plug in your own stuff, it was not haughty or insistent that you do things a certain way, it did not rewrite Python's whole standard library as many other frameworks practically rewrite the standard libraries of their constituent languages; it just stayed out of my way and let me do things the way I wanted while still providing me the infrastructure to get something published to the web pretty quickly.
This blog post seems to indicate that Pylons is going more in the direction of most frameworks with its talk of "full stack" and choosing defaults. Is Pylons going to become a reimplementation of Django? It's a little weird. I don't know why Pylons thinks this is better as a single project.
Re: TurboGears joins the Pylons Project
#6A bit unsettling for me. I use Pylons on several projects, though I haven't kept up with Pylons news. I really like Pylons because it was to me the best representation of the ideal framework out there; it was flexible and easy to plug in your own stuff, it was not haughty or insistent that you do things a certain way, it did not rewrite Python's whole standard library as many other frameworks practically rewrite the…
[deleted]
Re: TurboGears joins the Pylons Project
#7In my opinion this weakens both projects. As the ultimate goal seems to be to build a new framework based on the two, this means that every code you write today using on of those frameworks will be legacy code soon.
Re: TurboGears joins the Pylons Project
#8[deleted]
Re: TurboGears joins the Pylons Project
#9For cross-referencing, this was also submitted here: http://news.ycombinator.com/item?id=2045684
Re: TurboGears joins the Pylons Project
#10A bit unsettling for me. I use Pylons on several projects, though I haven't kept up with Pylons news. I really like Pylons because it was to me the best representation of the ideal framework out there; it was flexible and easy to plug in your own stuff, it was not haughty or insistent that you do things a certain way, it did not rewrite Python's whole standard library as many other frameworks practically rewrite the…
I think you're missing what they are doing.
Pyramid is repoze.bfg with some of the good things from Pylons added in. Pyramid is much more extensible with hooks. TurboGears will still be a full-stack, Pyramid + their choices for form library, templating, etc. Pyramid is still very light and makes very few assumptions.
I think it is better since you've brought together three frameworks and that collective mindshare is going to collaborate rather than compete.