On Wednesday, November 28, 2012 1:45:37 PM UTC-5, Mike Orr wrote:
> The Pylons Book is a product of its time. Maybe we should just release
> Pylons 1.2 unchanged to eliminate confusion. The Pylons Book *is* thorough
> and well-written, but it's dated and a couple chapters delved into esoteric
> areas (the author's unique libraries).
Honestly, I think that might be a good idea...
But I think maybe a big warning on the official Pylons Docs /migrations
guides. specifically these 2 pages:
just something like :
"Please note that Pylons Framework is at version 1.0.1 , while the
PylonsBook version 1.1 covers the PylonsFramework 0.9.7. Some
documentation on the PylonsBook 1.1 is out of date and incompatible with
the PylonsFramework 1.0.1."
> My first recommendation to people would be to just use Pyramid, which is
> "Pylons 2". If they want to use Pylons, they should read the online docs,
> and be aware that some gaps have appeared. (Some links to third-party
> documentation are dead, and "go-pylons.py was lost and no longer works so
> you'll have to install a virtualenv and Pylons manually.)
I agree with that, but the bulk of people I saw confused / having issues
(including myself) were those who were migrating legacy apps to 1.0.1 for
maintenance. The Book unfortunately has a lot of SEO. If you search for
migration help on random issues, the book's out-of-date docs come up... and
folks on StackOverflow are very good and pointing to the Out Of Date docs
based on the Book's version number.