31–40 of 42 posts
The simple fact is that the larger Python community never really cared for repoze.bfg and TurboGears. The Pylons, BFG and TurboGears teams joining forces feels more like a last, somewhat desparate move to garner some attention for projects that never reached critical mass. I don't think it'll change much of anything. I used to do development in Pylons and I've tried my hand at Pyramid, and there's simply nothing to g…
Earlier quoted context omitted.
I know on the surface that it does, but Pyramid isn't ready for production as yet. Also, the secondary issue for me is that I had made a choice to go with Pylons, but that has effectively been abandoned (sorry for the strong word as I appreciate it will be 'maintained' but will never move forward from where it is, and my concern is that after investing considerable time/energy into our project that the same thing cou…
Pyramid 1.0 final will be out before PyCon US (~ 2 months from now). However, it bears saying that, so far, no alpha release of Pyramid has been bw incompat with the last in any way. As a result, I wouldn't be scared off much by "alpha" in its version designator, at least as an evaluator. The code in Pyramid has existed for almost 2 years now. Every release has 100% statement coverage via unit tests. An alpha of Pyra…
Thanks again though. Looking forward to trying out Pyramid
Wow, I'm thoroughly confused as to which way to go with Python and web frameworks now. We do a fair bit of Python work, primarily for back-end processing (our main work is still in PHP) and we've been trying to move more to Python. I did a LOAD of research into frameworks and had chosen to go with Pylons, and then I saw that they were becoming Pyramid. This announcement obviously means three of them are merging toget…
I came to the same conclusion that I wanted to try out Pylons a few weeks ago right around the same time the repoze.bfg + Pylons merger was announced and just decided to jump into Pyramid. Recently I've been really impressed with the flexibility the platform offers allowing me to use all the libraries I had planned on and to make design decisions that I'm comfortable with. Initially there was quite a big learning cur…
Earlier quoted context omitted.
Hi Chris. Off the top of my head, from when I was working on a Pyramid app ~ a month ago: - No clear visual distinction between links to glossary terms and links to further documentation. I like the glossary, but always ended up there without wanting to. - I did find the tutorials, no issue there. (Only that the paster templates are a bit awkwardly named, but that's not a doc issue.) - Especially the former BFG stuff…
"No clear visual distinction between links to glossary terms": yep, fixed a while back. Glossary terms are now green, other links are blue. Traversal explaining: we're working on it (really). The docs have been rearranged and massaged a good bit, and they're being futher (professionally) edited now. Flexibility: the best I can do about that without betraying the goals of the project is http://docs.pylonshq.com/pyrami…
Wow, I'm thoroughly confused as to which way to go with Python and web frameworks now. We do a fair bit of Python work, primarily for back-end processing (our main work is still in PHP) and we've been trying to move more to Python. I did a LOAD of research into frameworks and had chosen to go with Pylons, and then I saw that they were becoming Pyramid. This announcement obviously means three of them are merging toget…
The simple fact is that the larger Python community never really cared for repoze.bfg and TurboGears. The Pylons, BFG and TurboGears teams joining forces feels more like a last, somewhat desparate move to garner some attention for projects that never reached critical mass. I don't think it'll change much of anything. I used to do development in Pylons and I've tried my hand at Pyramid, and there's simply nothing to g…
There is a lot that can be said for consolidation. And a lot to be said for the team working on pyramid now, so I'm excited in spite of your skepticism.
Earlier quoted context omitted.
As the author, I'm interested in improving the Pyramid docs. Can you elaborate on your issues with them? Did you notice the tutorials at http://docs.pylonshq.com/pyramid/dev/index.html#tutorials (lots of people seem to miss them).
Hi Chris. Off the top of my head, from when I was working on a Pyramid app ~ a month ago: - No clear visual distinction between links to glossary terms and links to further documentation. I like the glossary, but always ended up there without wanting to. - I did find the tutorials, no issue there. (Only that the paster templates are a bit awkwardly named, but that's not a doc issue.) - Especially the former BFG stuff…
The responsiveness of Chris and Ben to actually fixing this kind of thing is amazing, and one of the major reasons we thought teaming up with them would be a good idea.
I used to do a lot of Pylons development, and although it was a great framework that gave you a bunch of ways to do just about anything, I always had lot of trouble figuring out the right way. Jarring especially considering the guiding Python principle of "There should be one - and preferably only one - obvious way to do it".
As a result, Pylons always felt like a big jumble of modules that were all sort-of right for what you wanted. I'm glad to see some of TG's full-stack opinionism coming into the fold. I hope all this merging will lead to something with the strengths of both projects, like the Rails+Merb merge.
Wow, I'm thoroughly confused as to which way to go with Python and web frameworks now. We do a fair bit of Python work, primarily for back-end processing (our main work is still in PHP) and we've been trying to move more to Python. I did a LOAD of research into frameworks and had chosen to go with Pylons, and then I saw that they were becoming Pyramid. This announcement obviously means three of them are merging toget…
want something bigger that provides a "full stack"? Django
One choice to solve that problem would be to all join Django, which is widely used, and has an active developer community. But they have a very strong point of view about how web applications should be developed, and as a result django isn't that flexible.
So, in the end what we need is a strong alternative to Django that is flexible, uses existing libraries to good effect, and just works. By joining together in the Pylons Project around the Pyramid framework, that's just what we're aiming to do.