5 ms·

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

by inovica 16y ago

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 together, but it does make me a bit nervous. I want to stick with Python, because I love it, but this is all making my head hurt a little!!! Anyone on here done a load of research/experimentation already and care to help me make some decisions :) ?

chrism 16y ago
Considering the three principals of three (previously-separate) systems are congregating around one (Pyramid), doesn't it make your decision a little easier rather than harder?
- inovica 16y ago
  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 could happen. Thanks though - I appreciate that in some respects it does seem an easier choice. I suppose thats where RoR works - they have one main framework to choose from (and a good one) whereas with Python there are a lot.
  - chrism 16y ago
    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 Pyramid is arguably much more stable than many "final" releases of other web frameworks.
    - inovica 16y ago
      Thanks. That's helped to clarify things much more than my own reading found. Maybe it would be a good idea to put something up on the various sites to signpost new people to? Thanks again though. Looking forward to trying out Pyramid
  - cd34 16y ago
    Remember the bulk of Pyramid is repoze.bfg - which is 1.5+ years old and has 100% test coverage. Pylons really hadn't had anything other than bugfixes in quite some time, and had some problems with stacked object proxies which would have required a fairly substantial rewrite. Whether you consider Pylons dead or just simply finished is a matter of semantics. I still think Pylons is an extremely capable platform and I don't think you should be afraid to touch it. There is still plenty of mindshare around for Pylons.
nek4life 16y ago
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 curve as I was unfamiliar with using paste, what traversal was and if I should use it, best method to configure my app, etc... Initially this was my only real criticism, the level of indecision this flexibility instills in a noob, but since then the devs have been actively working on the docs to make them more beginner friendly and I've gotten some really great help in the irc channel. I'd say it's definitely worth taking a look if you were interested in Pylons.
- inovica 16y ago
  Thanks for this. It really helps me to make a decision. All the best
reinhardt 16y ago
Just go with Django. For all its warts (and there are a lot), it beats the hodgepodge of the agnostic glue frameworks and the one dozen or five external dependencies they bring in to get anything done.
mkramlich 16y ago
want something small that stays out of your way? web.py want something bigger that provides a "full stack"? Django

by inovica 16y ago

chrism 16y ago

Considering the three principals of three (previously-separate) systems are congregating around one (Pyramid), doesn't it make your decision a little easier rather than harder?

inovica 16y ago
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 could happen. Thanks though - I appreciate that in some respects it does seem an easier choice. I suppose thats where RoR works - they have one main framework to choose from (and a good one) whereas with Python there are a lot.
- chrism 16y ago
  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 Pyramid is arguably much more stable than many "final" releases of other web frameworks.
  - inovica 16y ago
    Thanks. That's helped to clarify things much more than my own reading found. Maybe it would be a good idea to put something up on the various sites to signpost new people to? Thanks again though. Looking forward to trying out Pyramid
- cd34 16y ago
  Remember the bulk of Pyramid is repoze.bfg - which is 1.5+ years old and has 100% test coverage. Pylons really hadn't had anything other than bugfixes in quite some time, and had some problems with stacked object proxies which would have required a fairly substantial rewrite. Whether you consider Pylons dead or just simply finished is a matter of semantics. I still think Pylons is an extremely capable platform and I don't think you should be afraid to touch it. There is still plenty of mindshare around for Pylons.

nek4life 16y ago

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 curve as I was unfamiliar with using paste, what traversal was and if I should use it, best method to configure my app, etc... Initially this was my only real criticism, the level of indecision this flexibility instills in a noob, but since then the devs have been actively working on the docs to make them more beginner friendly and I've gotten some really great help in the irc channel. I'd say it's definitely worth taking a look if you were interested in Pylons.

inovica 16y ago
Thanks for this. It really helps me to make a decision. All the best

reinhardt 16y ago

Just go with Django. For all its warts (and there are a lot), it beats the hodgepodge of the agnostic glue frameworks and the one dozen or five external dependencies they bring in to get anything done.

mkramlich 16y ago

want something small that stays out of your way? web.py want something bigger that provides a "full stack"? Django