Pylons & repoze.bfg Merge • Hacker News Board

Re: Pylons & repoze.bfg Merge

#31

Post by windle » Sat, Nov 06, 2010, 8:55 PM UTC

mdda wrote: post #30

windle wrote: post #28

Earlier quoted context omitted.

As mentioned below, there's no "leaving" involved. The pylons code-base has been maintained for several years with little in the way of new features, just bug fixes, some minor clean-ups, and security fixes. That isn't changing... so there's nothing 'different' for the pylons code-base involved. I'm confused where this notion of leaving pylons comes from, when nothing is changing with it.

Last week I bought a top-of-the-range camera from Nikon. Excellent camera in every way : Great purchase. This week, Nikon has discontinued the camera, and has announced that there's going to be a new range, even better, coming along soon. Do I now love my camera as much as I used to? Rationally, my opinion shouldn't have changed. But I sure wish that I had known that my investment in the previous product was a dead-e…

Not quite the same, because the new version has a bunch of features added. If you'd like to stick with the camera analogy, you should think of the pylons framework more as a good lens for the DSLR. Most of the features are from the body, so you upgrade that and keep using the same lens.

The Pylons framework was almost entirely just glue between your choices of ORM/templates along with using WebHelpers and Beaker. Those projects are still in use with pyramid, still getting updates (and thus a pylons project will still get feature updates via them).

I tried to explain this better here: http://groups.google.com/group/pylons-discuss/browse_thread/...

Re: Pylons & repoze.bfg Merge

#32

Post by rbp » Sat, Nov 06, 2010, 10:36 PM UTC

wow - no new features in the last 2 years. web2py seems to get a new feature every week even though they promise backwards compatibility.

Re: Pylons & repoze.bfg Merge

#33

Post by windle » Sat, Nov 06, 2010, 10:53 PM UTC

jtchang wrote: post #29

If anyone happens to be in the bay area and is interested in a meetup to sit down and learn repoze.bfg and the differences between pylons let me know. I think it would helpful to get a bunch of us Pylons users together and talk about it.

I agree, I'm in the North Bay, and I'd be open to helping people work through pyramid, and discussing things in person. Would a meet-up next Thursday night (the 11th) work for some folks? Maybe around the South Bay or SF if someone can get some space?

Re: Pylons & repoze.bfg Merge

#34

Post by windle » Sun, Nov 07, 2010, 4:40 PM UTC

rbp wrote: post #32

wow - no new features in the last 2 years. web2py seems to get a new feature every week even though they promise backwards compatibility.

I think you missed the bit about Pylons being a 'glue' framework between other packages. Those packages have gotten quite a few new features over the years, and they continue to get new features regardless of whether Pylons users use them.

This is the kind of nice thing about using multiple open-source packages that are in heavy use throughout the Python world beyond just web frameworks (unlike web2py).

Re: Pylons & repoze.bfg Merge

#35

Post by cd34 » Mon, Nov 08, 2010, 2:09 AM UTC

Keith83 wrote: post #15

windle wrote: post #13

Earlier quoted context omitted.

Depending on what you're prototyping, it could very well be done faster with Django. Django provides a bunch of 'generic views' which can make tossing up lists of objects from the db very fast to get started with. Then usually you end up fully replacing it all later, but it gives you a good start. My views haven't changed since I answered this: http://stackoverflow.com/questions/48681/pros-cons-of-django... If your a…

To help make the move from Pylons, I'd love to see a document introducing Pyramid from a Pylons perspective and explaining what it does differently. Please say Pyramid has a debug mode like Pylons :)

easy_install weberror, tempita, pygments

add egg:WebError#evalerror into your pipeline. It isn't in the default Pyramid paster template, but, it was mentioned that it will probably be included in in the default Pyramid paster templates. http://goo.gl/EDqNo is a document I wrote regarding the transition of a Pylons 1.0 to Pyramid 1.0a1 application.