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
Pyramid has the advantage that its official docs are already the length and
quality of a book, and I think an earlier version of it (the BFG manual)
was even published. Now it's essentially a print-it-yourself book.
The Pylons Book is a product of its time. Maybe we should just release
Pylons 1.2
I was going batty today trying to figure out why documentation ,
recommendations, and changelogs were conflicting when migrating an old
Pylons project.
Then I finally realized the problem - and noticed a large number of
people on StackOverflow were suffering from the same issue:
- The Pylons
Pyramid could consider doing what Kevin Dangoor said a while back--If it's not
documented, it doesn't exist!
http://markmail.org/message/ep3hfpx7cnxy7g5d
Tim
--
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To view this discussion on the
On 11/27/2012 11:47 PM, timblack1 wrote:
Pyramid could consider doing what Kevin Dangoor said a while back--If it's not
documented, it doesn't exist!
Already true.
- C
--
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group,
