3 ms·
I used django-tastypie to create our restful API at work. It turned into a "round peg square hole" situation. In over half of my end points I had to over ride t
by richardlblair 14y ago
I used django-tastypie to create our restful API at work. It turned into a "round peg square hole" situation. In over half of my end points I had to over ride the default behaviour. This goes right down to how URL are generated. I spent a lot of time reading code.
So while it is very powerful, I probably won't be using it again for a large project.
- richardlblair 14y agoI'm also not very happy with the XML serialization. (I know, I know, it's XML. But people still use it.)
- prayag 14y agoThis is exactly my experience. When we were writing the first version of the API for MobileWorks I chose django-tastypie. Within a few months we had overridden most of the default behavior and a lot of my time was spent studying the code-base of tasypie (which is fantastic BTW). When it was time to write a new version, I decided to start from a clean slate and write it ourselves from grounds-up. We don't have some of the functionality that tasty-pie provided us out of the box but the maintenance and new features are extremely fast to write.
- richardlblair 14y agoWe are about to do the exact same thing. Tastypie was a good decision to begin with, but as our project evolves it becomes unrealistic.