读者，因为我们都将成为知识的传承者。 致谢 - 2 - 本文档使用 书栈(BookStack.CN) 构建 README Django-intro-zh Django 官方教程翻译项目 目前版本：1.11 官方文档目录 中文版文档 翻译进度 我也想一起翻译 这个项目的目的是将 Django 官方教程的 intro 部分 翻译成中文版。 起因是在看完 Django Book 之后 通俗易懂。为了方便更多想要学习 Django 的人（顺便翻译一遍也能更深入的理解文档），就有了 这个项目。 这一项目离不开辛勤帮助翻译的小伙伴们，没有他们这个项目也无法完成。 特别感谢 @Zoctan，将翻译版本从 1.8 升级到了 1.11（pr），跟上了 Django 的发展。 官方文档 在此。 以下是官方文档的目录： Django at a glance Quick install guide Advanced tutorial: How to write reusable apps What to read next Django-intro-zh Django 官方教程翻译项目 目前版本：1.11 官方文档目录 README - 3 - 本文档使用 书栈(BookStack.CN) 构建 Writing your first patch for Django 中文版文档请到

逻辑的文章。 一篇是你在开始动手搭建环境前需要了解各工具原理的文章。 这是一篇你真正开始前需要查阅的文章。 本文介绍了前后端工作原理，前后端搭建的流程、搭建过程中需要用到的技术以及 开发环境版本。 一、前后端如何工作 Django、Vue 和 Element UI 前后 端原理论述  作者：M&T. 2 《51 测试天地》七十四 www.51testing.com 后端开发（Django+Rest Pipenv 等工具来管理项目的依赖，这样 可以确保项目在不同环境中安装相同的依赖版本，从而避免由于依赖版本不一致而引发 的错误。 提高项目可移植性：将项目的依赖放在虚拟环境中，可以使得项目在不同的计算机 或服务器上都能轻松地部署和运行，而不需要担心依赖问题。 简化依赖管理：虚拟环境可以将项目所需的依赖以及其版本信息保存在一个文件中 （例如 Pipfile.lock），这样可以方便地重现项目的开发环境，使得依赖的安装和管理更加 51testing.com 管理依赖：Pipenv 会自动地管理项目的依赖关系，并将依赖信息保存在 Pipfile 和 Pipfile.lock 文件中，这样可以确保项目在不同环境中安装相同的依赖版本。 简化依赖安装：使用 Pipenv 安装依赖非常简单，只需要运行一个命令即可，而不需 要手动管理依赖的安装。 提供更友好的命令行界面：Pipenv 提供了一组易于使用的命令，使得包管理和虚拟

high-quality Web application. Django encourages beautiful URL design and doesn’t put any cruft in URLs, like .php or .asp. To design URLs for an app, you create a Python module called a URLconf. A table of contents variable. In this case, the date filter formats a Python datetime object in the given format (as found in PHP’s date function). You can chain together as many filters as you’d like. You can write custom template with a built-in Python package). Where should this code live? If your background is in plain old PHP (with no use of modern frameworks), you’re probably used to putting code under the Web server’s document

high-quality Web application. Django encourages beautiful URL design and doesn’t put any cruft in URLs, like .php or .asp. To design URLs for an app, you create a Python module called a URLconf. A table of contents variable. In this case, the date filter formats a Python datetime object in the given format (as found in PHP’s date function). You can chain together as many filters as you’d like. You can write custom template with a built-in Python package). Where should this code live? If your background is in plain old PHP (with no use of modern frameworks), you’re probably used to putting code under the Web server’s document

high-quality Web application. Django encourages beautiful URL design and doesn’t put any cruft in URLs, like .php or .asp. To design URLs for an app, you create a Python module called a URLconf. A table of contents variable. In this case, the date filter formats a Python datetime object in the given format (as found in PHP’s date function). You can chain together as many filters as you’d like. You can write custom template with a built-in Python package). Where should this code live? If your background is in plain old PHP (with no use of modern frameworks), you’re probably used to putting code under the Web server’s document

high-quality Web application. Django encourages beautiful URL design and doesn’t put any cruft in URLs, like .php or .asp. To design URLs for an app, you create a Python module called a URLconf. A table of contents variable. In this case, the date filter formats a Python datetime object in the given format (as found in PHP’s date function). You can chain together as many filters as you’d like. You can write custom template with a built-in Python package). Where should this code live? If your background is in plain old PHP (with no use of modern frameworks), you’re probably used to putting code under the Web server’s document

high-quality web application. Django encourages beautiful URL design and doesn’t put any cruft in URLs, like .php or .asp. To design URLs for an app, you create a Python module called a URLconf. A table of contents variable. In this case, the date filter formats a Python datetime object in the given format (as found in PHP’s date function). You can chain together as many filters as you’d like. You can write custom template with a built-in Python package). Where should this code live? If your background is in plain old PHP (with no use of modern frameworks), you’re probably used to putting code under the web server’s document

high-quality web application. Django encourages beautiful URL design and doesn’t put any cruft in URLs, like .php or .asp. To design URLs for an app, you create a Python module called a URLconf. A table of contents variable. In this case, the date filter formats a Python datetime object in the given format (as found in PHP’s date function). You can chain together as many filters as you’d like. You can write custom template and solely, cookie-based. It does not fall back to putting session IDs in URLs as a last resort, as PHP does. This is an intentional design decision. Not only does that behavior make URLs ugly, it makes

high-quality web application. Django encourages beautiful URL design and doesn’t put any cruft in URLs, like .php or .asp. To design URLs for an app, you create a Python module called a URLconf. A table of contents variable. In this case, the date filter formats a Python datetime object in the given format (as found in PHP’s date function). You can chain together as many filters as you’d like. You can write custom template and solely, cookie-based. It does not fall back to putting session IDs in URLs as a last resort, as PHP does. This is an intentional design decision. Not only does that behavior make URLs ugly, it makes

high-quality Web application. Django encourages beautiful URL design and doesn’t put any cruft in URLs, like .php or .asp. To design URLs for an app, you create a Python module called a URLconf. A table of contents variable. In this case, the date filter formats a Python datetime object in the given format (as found in PHP’s date function). You can chain together as many filters as you’d like. You can write custom template with a built-in Python package). Where should this code live? If your background is in plain old PHP (with no use of modern frameworks), you’re probably used to putting code under the Web server’s document