Django 通用视图，设计指南
我承认这个问题有点主观，并且它没有指出某些技术疑问/疑问，但我想知道。
我是 django 的新手，在 django 中开发应用程序 3-4 个月后，我正在尝试深入挖掘。 我目前正在阅读 James Brennet 写的书，他在其中展示了如何使用通用视图，但是当我头到 https://docs.djangoproject.com/en/dev/topics/ 我请参阅通用视图已被废弃。
从“最佳设计角度”的角度来看，如何评价使用通用视图？
使用通用视图是否被认为是一种好的做法？
如果是的话，为什么 django 会贬低它呢？
如果没有，还有什么推荐的？
谢谢！
I accept that the question is a bit subjective, and that it does not pin point at certain technical doubt/query, but i wanted to know.
I am a newbie in django, after 3-4 months of doing apps in django i am trying to dig-down-deep.
I am currently reading a book by James Brennet where he shows how to use generic views, but when i head to https://docs.djangoproject.com/en/dev/topics/ i see generic views are depricated.
From the "best design perspective" point of view, how is using generic views rated?
Is it considered a good practice to use generic views?
If yes why is then django depricating it?
If no, what else is recommended?
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
旧的通用视图已被弃用，因为它们已被“基于类的通用视图”取代：
https://docs.djangoproject.com/en/dev/topics/ class-based-views/
如果您有很多重复表达相同模式的视图，例如多个模型的一组 CReate/Update/Delete (CRUD) 视图...其中大部分视图代码是相同的，但只是一些细节更改，例如模型类和最终重定向 URL...这是通用视图有意义的地方。
目标是 DRY（不要重复自己）……即在一个地方编写代码并在一个地方重用、捕获和修复错误等。
The old generic views are deprecated because they've been replaced with 'Class-based generic views':
https://docs.djangoproject.com/en/dev/topics/class-based-views/
If you have a lot of view which repeatedly express the same pattern, for example a set of CReate/Update/Delete (CRUD) views for several models... where most of the view code is the same but just some specifics change, eg the model class and final redirect url... this is where generic views make sense.
The goal is to be DRY (Don't Repeat Yourself) ...ie write the code in one place and re-use, catch and fix bugs in one place etc.