That django-piston is 'stable' means work outside of maintenance has ceased. Which means a lot of people are going to this post to figure out what django-piston should do out of the box.
So now you've gone from "I don't want to be negative..." to full-on anti-Piston zealot? Looks like you just edited that post,
> Critical Update 2012/05/10!!!
> Critical Update 2012/05/10!!!
> Critical Update 2012/05/10!!!
(I guess you wanted one line per exclamation point there)
> Except for a critical security patch, django-piston has been unsupported for about 3 years. That is an eternity, and the number of forks to address multiple issues is cause for alarm. Also, the original author has left the project. Because of that, in it's place at this time I recommend django-tastypie. It is up-to-date, has very good documentation, supports OAUTH, and scored second place in the Django Packages thunderdome (it got nearly 3x as many points!). Another tool to consider is Django Rest Framework, which is as good as django-tastypie but lacks the OAUTH support.
And I had a different Critical Update on that blog post for over 10 months with a harsher warning. I changed it today because I still had seen no progress but felt I should tone it down.
If the django-piston community updates and documents, I'll post something nicer. In the meantime, the critical update remains.
See my article at http://pydanny.blogspot.com/2010/07/getting-piston-forms-to-... which STILL gets a lot of hits.
That django-piston is 'stable' means work outside of maintenance has ceased. Which means a lot of people are going to this post to figure out what django-piston should do out of the box.