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-end.

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/...