blocks|key|791412|text|两者都是不错的选择。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|791413|对于过滤器来说，tastypie开箱即用功能更强大。如果你有一个公开模型的视图，你可以做Django风格的不等式过滤器：|791414|http://www.example.com/api/person?age__gt=30|code-block|syntax|javascript|791415|或或查询：|791416|http://www.example.com/api/mymodel?language__in=en&language__in=fr|791417|使用djangorestframework可以做到这一点，但您必须为每个模型编写自定义过滤器。|791418|对于回溯，我对django-rest-framework印象更深。当DEBUG+=+False出现异常时，Tastypie会尝试向settings.ADMINS发送电子邮件。当DEBUG+=+True，the+default+error+message+is+serialised+JSON时，它更难读。|offset|length|style|CODE|791419|entityMap|0|LINK|mutability|MUTABLE|url|http://django-tastypie.readthedocs.org/en/latest/settings.html#tastypie-full-debug^0|0|0|0|0|0|0|Y|D|1T|F|2G|C|2T|18|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|15|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|16|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|18|8|@$Q|19|R|1A|S|T]|$Q|1B|R|1C|S|T]|$Q|1D|R|1E|S|T]]|9|@$Q|1F|R|1G|1|1H]]|A|$]]|$1|U|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

Both are good choices.

For filters, tastypie is more powerful out-of-the-box. If you have a view that exposes a model, you can do Django-style inequality filters:

<pre><code>http://www.example.com/api/person?age__gt=30
</code></pre>

or OR queries:

<pre><code>http://www.example.com/api/mymodel?language__in=en&amp;language__in=fr
</code></pre>

these are possible with djangorestframework, but you have to write custom filters for each model.

For tracebacks, I've been more impressed with django-rest-framework. Tastypie tries to email <code>settings.ADMINS</code> on exceptions when <code>DEBUG = False</code>. When <code>DEBUG = True</code>, <a href="http://django-tastypie.readthedocs.org/en/latest/settings.html#tastypie-full-debug" rel="noreferrer">the default error message is serialised JSON</a>, which is harder to read.

blocks|key|791503|text|值得注意的是，自从第一次被问到这一点以来，DRF已经变得越来越强大。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|791504|它在github上是两个中更活跃的一个(都是在提交，星形，分支和贡献者方面)|791505|DRF支持OAuth+2和可浏览的API。|791506|老实说，对我来说，最后一个特性才是杀手锏。当我的前端开发人员不确定某些东西是如何工作的时候，他们能够将所有的前端开发人员都指向可浏览的API，并说“去玩吧；找出答案”，这真是太棒了。|791507|尤其是因为这意味着他们可以按照自己的方式理解它，并知道API确实、绝对、绝对地做了“文档”所说的事情。在与API集成的世界中，这一事实本身就使DRF成为值得击败的框架。|791508|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

It's worth noting that since this was first asked DRF has gone from strength to strength.

It's the more active of the two on github (both in terms of commits, stars, forks and contributors)

DRF has OAuth 2 support and the browsable API.

Honestly for me that last feature is the killer. Being able to point all my front-end devs at the browsable API when they aren't sure how something works and say 'Go play; find out' is fantastic.

Not least because it means they get to understand it on their own terms and know that the API really, definitely, absolutely does what the 'documentation' says it does. In the world of integrating with APIs, that fact alone makes DRF the framework to beat.

blocks|key|791543|text|在使用了这两个框架之后，我喜欢(更喜欢)+Django+Rest+Framwork的一点是它与Django非常一致。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|791544|编写模型序列化程序与编写模型窗体非常相似。内置的通用视图与Django的HTML通用视图非常相似。|791545|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Having used both, one thing that I liked (preferred) about Django Rest Framwork is that is is very consistent with Django. 

Writing model serializers is very similar to writing model forms. The built in Generic Views are very similar to Django's generic views for HTML.

blocks|key|575350|text|Django-tastypie不再由它的原始创建者维护，他创建了自己的一个新的轻量级框架。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|575351|目前，如果你愿意公开你的API，你应该在django中使用django-rest-framework。|575352|大公司正在使用它。django-rest-framework是django团队的核心成员，他获得了维护django-rest-framework的资金。|575353|django-rest-framework也有大量不断增长的第三方艺术包，这将帮助你以更少的麻烦更容易地构建API。|575354|drf的一些部分也将被合并到django本身。|575355|drf提供了比django-tastypie更好的模式和工具。|575356|简而言之，它设计良好，维护良好，资金充足，提供了巨大的第三方应用程序，受到大型组织的信任，更容易，更少的样板等等。|575357|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

Django-tastypie is no longer maintained by it's original creator and he created a new light weight framework of his own.

At present you should use django-rest-framework with django if you are willing to expose your API.

Large corporations are using it. django-rest-framework is a core member of django team and he get funding to maintain django-rest-framework.

django-rest-framework also have huge number of ever growing 3rd arty packages too which will help you build your API's more easily with less hassles.

Some part of drf will also be merged in django proper.

drf provide more better patterns and tools then django-tastypie.

In short it's well designed, well maintained, funded, provide huge 3rd party apps, trusted by large organisations, easier and less boilerplate etc over tastypie.

Why would you use one over the other, for exposing an API for your Django app?

<a href="http://pypi.python.org/pypi/djangorestframework/" rel="noreferrer">http://pypi.python.org/pypi/djangorestframework/</a>

<a href="http://pypi.python.org/pypi/django-tastypie" rel="noreferrer">http://pypi.python.org/pypi/django-tastypie</a>

What are the differences between django-tastypie and djangorestframework?

Django

OAuth

为什么你要用一个来暴露你的Django应用程序的API呢？

问django-tastypie和djangorestframework有什么不同？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问django-tastypie和djangorestframework有什么不同？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问django-tastypie和djangorestframework有什么不同？
EN