3 ms·
A 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 represe
by cookiecaper 16y ago
A 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.
- deleted 16y ago[deleted]
- cd34 16y agoI 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.
- sankyo 16y agoI have been digging into the pyramid docs and writing some toy apps with it trying to learn it, and I think that you will not be disappointed. I am confident that turbogears / tosca widgets will be integrated in such a way that it is loosely coupled and will not get in your way if you do not want to use it. Spend some time reading the pyramid docs - it it totally agnostic for template engines, authentication/authorization, http session implementation, etc. very pluggable. I will say though, that at this point 1.0alpha8, a noob will probably get frustrated, but someone who has worked with pylons / repoze / sqlalchemy can connect the dots. Also, with every alpha release, you can also see the changes to the documentation, which is looking more like django docs (i.e. good) Django fills a certain niche and if it matches your problem, it is a no brainer. If you need a more flexible web framework, look at pyramid.