Django 1.11 官方文档：入门与实战指南

4星 · 超过85%的资源需积分: 10 189 浏览量更新于2024-07-19 2 收藏 6.3MB PDF 举报

"django 1.11 官方说明文档.pdf 电子书" 这份文档是Django 1.11版本的官方指南，由Django Software Foundation发布，日期为2017年7月10日。Django是一个用Python编写的高级Web框架，它鼓励快速开发和干净、实用的设计，旨在使开发者能够构建功能强大的Web应用。文档内容分为多个部分，详细介绍了Django的各个方面： 1. **获取帮助**：提供了如何在遇到问题时寻求解答的途径。 2. **文档组织结构**：解释了文档的布局和各个部分的内容。 3. **初学者入门**：指导新用户如何开始使用Django。 4. **模型层**：介绍了Django的ORM（对象关系映射）系统，用于管理数据库。 5. **视图层**：阐述了处理HTTP请求并返回响应的视图函数或类。 6. **模板层**：讨论了Django的模板语言，用于生成动态HTML。 7. **表单**：展示了如何创建和使用表单数据处理。 8. **开发过程**：涵盖开发环境的设置和最佳实践。 9. **管理后台**：讲解了如何自动生成强大的后台管理系统。 10. **安全性**：提到了Django的安全特性及如何防止常见的Web攻击。 11. **国际化与本地化**：讨论如何使应用适应多种语言和地区。 12. **性能与优化**：提供了一些提高Django应用性能的策略。 13. **Python兼容性**：确认Django 1.11支持的Python版本。 14. **地理框架**：如果涉及到地理位置信息，这部分会提供相关信息。 15. **常用Web应用工具**：介绍Django提供的辅助工具和中间件。 16. **其他核心功能**：涵盖了文档未专门提及的其他关键特性。 17. **Django开源项目**：简述Django社区、贡献和版本控制。文档的第二部分是**开始使用Django**，包含了以下子章节： - **Django概述**：快速了解Django的基本概念和工作方式。 - **快速安装指南**：指导如何在系统上安装Django。 - **编写你的第一个Django应用，第一部分到第七部分**：这是一个逐步教程，教你从零开始创建一个完整的Django应用，包括模型、视图、模板、URL配置等。 - **进阶教程：如何编写可重用的应用**：对于有经验的开发者，提供了更深入的指导，教你如何创建可复用的Django应用组件。接下来的章节可能是建议读者继续阅读的内容，但具体信息未给出。这份详尽的文档是学习和掌握Django 1.11的基础，无论你是初学者还是有经验的开发者，都能从中受益。

Django Documentation, Release 1.11.4.dev20170710184915

The philosophy here is that your site is edited by a staff, or a client, or maybe just you – and you don’t want to have to

deal with creating backend interfaces just to manage content.

One typical workﬂow in creating Django apps is to create models and get the admin sites up and running as fast as

possible, so your staff (or clients) can start populating data. Then, develop the way data is presented to the public.

Design your URLs

A clean, elegant URL scheme is an important detail in a 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 for your app, it contains

a simple mapping between URL patterns and Python callback functions. URLconfs also serve to decouple URLs from

Python code.

Here’s what a URLconf might look like for the Reporter/Article example above:

mysite/news/urls.py

from django.conf.urls import url

from . import views

urlpatterns = [

url(r'^articles/([0-9]{4})/$', views.year_archive),

url(r'^articles/([0-9]{4})/([0-9]{2})/$', views.month_archive),

url(r'^articles/([0-9]{4})/([0-9]{2})/([0-9]+)/$', views.article_detail),

]

The code above maps URLs, as simple regular expressions, to the location of Python callback functions (“views”).

The regular expressions use parenthesis to “capture” values from the URLs. When a user requests a page, Django runs

through each pattern, in order, and stops at the ﬁrst one that matches the requested URL. (If none of them matches,

Django calls a special-case 404 view.) This is blazingly fast, because the regular expressions are compiled at load

time.

Once one of the regexes matches, Django imports and calls the given view, which is a simple Python function. Each

view gets passed a request object – which contains request metadata – and the values captured in the regex.

For example, if a user requested the URL “/articles/2005/05/39323/”, Django would call the function news.views.

article_detail(request, '2005', '05', '39323').

Write your views

Each view is responsible for doing one of two things: Returning an HttpResponse object containing the content

for the requested page, or raising an exception such as Http404. The rest is up to you.

Generally, a view retrieves data according to the parameters, loads a template and renders the template with the

retrieved data. Here’s an example view for year_archive from above:

mysite/news/views.py

from django.shortcuts import render

from .models import Article

def year_archive(request, year):

a_list = Article.objects.filter(pub_date__year=year)

context = {'year': year, 'article_list': a_list}

return render(request, 'news/year_archive.html', context)

10 Chapter 2. Getting started

Django Documentation, Release 1.11.4.dev20170710184915

This example uses Django’s template system, which has several powerful features but strives to stay simple enough

for non-programmers to use.

Design your templates

The code above loads the news/year_archive.html template.

Django has a template search path, which allows you to minimize redundancy among templates. In your Django

settings, you specify a list of directories to check for templates with DIRS. If a template doesn’t exist in the ﬁrst

directory, it checks the second, and so on.

Let’s say the news/year_archive.html template was found. Here’s what that might look like:

mysite/news/templates/news/year_archive.html

{% extends "base.html" %}

{% block title %}Articles for {{ year }}{% endblock %}

{% block content %}

<h1>Articles for {{ year }}</h1>

{% for article in article_list %}

<p>{{ article.headline }}</p>

<p>By {{ article.reporter.full_name }}</p>

<p>Published {{ article.pub_date|date:"F j, Y" }}</p>

{% endfor %}

{% endblock %}

Variables are surrounded by double-curly braces. {{ article.headline }} means “Output the value of the

article’s headline attribute.” But dots aren’t used only for attribute lookup. They also can do dictionary-key lookup,

index lookup and function calls.

Note {{ article.pub_date|date:"F j, Y" }} uses a Unix-style “pipe” (the “|” character). This is called

a template ﬁlter, and it’s a way to ﬁlter the value of a variable. In this case, the date ﬁlter formats a Python datetime

object in the given format (as found in PHP’s date function).

You can chain together as many ﬁlters as you’d like. You can write custom template ﬁlters. You can write custom

template tags, which run custom Python code behind the scenes.

Finally, Django uses the concept of “template inheritance”. That’s what the {% extends "base.html" %}

does. It means “First load the template called ‘base’, which has deﬁned a bunch of blocks, and ﬁll the blocks with

the following blocks.” In short, that lets you dramatically cut down on redundancy in templates: each template has to

deﬁne only what’s unique to that template.

Here’s what the “base.html” template, including the use of static ﬁles, might look like:

mysite/templates/base.html

{% load static %}

<html>

<head>

<title>{% block title %}{% endblock %}</title>

</head>

<body>

{% block content %}{% endblock %}

</body>

</html>

2.1. Django at a glance 11

Django Documentation, Release 1.11.4.dev20170710184915

Simplistically, it deﬁnes the look-and-feel of the site (with the site’s logo), and provides “holes” for child templates to

ﬁll. This makes a site redesign as easy as changing a single ﬁle – the base template.

It also lets you create multiple versions of a site, with different base templates, while reusing child templates. Django’s

creators have used this technique to create strikingly different mobile versions of sites – simply by creating a new base

template.

Note that you don’t have to use Django’s template system if you prefer another system. While Django’s template

system is particularly well-integrated with Django’s model layer, nothing forces you to use it. For that matter, you

don’t have to use Django’s database API, either. You can use another database abstraction layer, you can read XML

ﬁles, you can read ﬁles off disk, or anything you want. Each piece of Django – models, views, templates – is decoupled

from the next.

This is just the surface

This has been only a quick overview of Django’s functionality. Some more useful features:

• A caching framework that integrates with memcached or other backends.

• A syndication framework that makes creating RSS and Atom feeds as easy as writing a small Python class.

• More sexy automatically-generated admin features – this overview barely scratched the surface.

The next obvious steps are for you to download Django, read the tutorial and join the community. Thanks for your

interest!

Quick install guide

Before you can use Django, you’ll need to get it installed. We have a complete installation guide that covers all

the possibilities; this guide will guide you to a simple, minimal installation that’ll work while you walk through the

introduction.

Install Python

Being a Python Web framework, Django requires Python. See What Python version can I use with Django? for details.

Python includes a lightweight database called SQLite so you won’t need to set up a database just yet.

Get the latest version of Python at https://www.python.org/downloads/ or with your operating system’s package man-

ager.

Django on Jython

If you use Jython (a Python implementation for the Java platform), you’ll need to follow a few additional steps. See

Running Django on Jython for details.

You can verify that Python is installed by typing python from your shell; you should see something like:

Python 3.4.x

[GCC 4.x] on linux

Type "help", "copyright", "credits" or "license" for more information.

>>>

12 Chapter 2. Getting started

Django Documentation, Release 1.11.4.dev20170710184915

• A public site that lets people view polls and vote in them.

• An admin site that lets you add, change, and delete polls.

We’ll assume you have Django installed already. You can tell Django is installed and which version by running the

following command in a shell prompt (indicated by the $ preﬁx):

$ python -m django --version

If Django is installed, you should see the version of your installation. If it isn’t, you’ll get an error telling “No module

named django”.

This tutorial is written for Django 1.11 and Python 3.4 or later. If the Django version doesn’t match, you can refer to

the tutorial for your version of Django by using the version switcher at the bottom right corner of this page, or update

Django to the newest version. If you are still using Python 2.7, you will need to adjust the code samples slightly, as

described in comments.

See How to install Django for advice on how to remove older versions of Django and install a newer one.

Where to get help:

If you’re having trouble going through this tutorial, please post a message to django-users or drop by #django on

irc.freenode.net to chat with other Django users who might be able to help.

Creating a project

If this is your ﬁrst time using Django, you’ll have to take care of some initial setup. Namely, you’ll need to auto-

generate some code that establishes a Django project – a collection of settings for an instance of Django, including

database conﬁguration, Django-speciﬁc options and application-speciﬁc settings.

From the command line, cd into a directory where you’d like to store your code, then run the following command:

$ django-admin startproject mysite

This will create a mysite directory in your current directory. If it didn’t work, see Problems running django-admin.

Note: You’ll need to avoid naming projects after built-in Python or Django components. In particular, this means

you should avoid using names like django (which will conﬂict with Django itself) or test (which conﬂicts 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 root (in a place such as /var/www). With Django, you don’t do that. It’s not a

good idea to put any of this Python code within your Web server’s document root, because it risks the possibility that

people may be able to view your code over the Web. That’s not good for security.

Put your code in some directory outside of the document root, such as /home/mycode.

Let’s look at what startproject created:

mysite/

manage.py

mysite/

14 Chapter 2. Getting started

剩余1849页未读，继续阅读

lishuhuakai

粉丝: 744
资源: 12

Django 1.11 官方文档：入门与实战指南

Django 1.11与channels 2.x：实时通讯与异步解决方案

Django 1.11官方文档详解

Django 1.11 官方文档精华解读

Django REST framework 中文文档.pdf

django 1.11版官方文档（英文）

Django1.11框架课件.zip

Django-1.11-py2.py3-none-any.whl

Django-1.11-en.zip

Django_by_Example.pdf.pdf

Django官方文档.pdf

最新资源