Django 1.8 官方文档精要

需积分: 10 129 浏览量更新于2024-07-20 收藏 5.87MB PDF 举报

"Django1.8官方文档" Django是一个基于Python的开源Web框架，它遵循模型-视图-控制器（MVC）的设计模式，旨在简化网页应用的开发过程，同时提供高效能和安全性。Django 1.8是该框架的一个版本，此文档包含了从基础到高级的全方位指南。 1.1 获取帮助 Django官方文档提供了多种获取帮助的途径，包括邮件列表、论坛、IRC聊天室以及Stack Overflow等在线社区，帮助用户在遇到问题时能够得到及时解答。 1.2 初步入门对于初学者，文档首先介绍了Django的基本概念和安装步骤，帮助开发者快速上手。 1.3 模型层模型层是Django数据持久化的核心，用于定义数据库中的表结构。在这里，你可以学习如何创建模型类、管理字段、定义关系，以及进行数据库迁移操作。 1.4 视图层视图是处理HTTP请求并返回响应的部分，负责业务逻辑和数据处理。文档详细解释了如何编写视图函数，以及如何通过URL配置关联视图。 1.5 模板层模板层是呈现HTML和动态内容的地方，Django的模板语言允许开发者轻松地插入变量、控制结构和过滤器来生成动态网页。 1.6 表单 Django提供了强大的表单处理功能，包括自动生成表单、验证用户输入、渲染HTML表单等。这使得处理用户提交的数据变得更加便捷。 1.7 开发流程官方文档详细描述了Django的开发流程，包括设置开发环境、调试技巧、测试策略等，旨在提升开发效率和代码质量。 1.8 管理后台 Django内置的管理后台可以让开发者轻松地管理数据库对象，进行添加、修改和删除操作。只需简单的配置，就能为每个模型生成管理界面。 1.9 安全性 Django重视安全性，文档中详细介绍了如何防止常见的Web攻击，如SQL注入、跨站脚本攻击（XSS）等，并提供安全配置建议。 1.10 国际化与本地化 Django支持多语言，提供了国际化的翻译机制和本地化时间、日期格式等功能，使应用能够适应全球用户的需求。 1.11 性能优化官方文档提供了性能调优的建议，如缓存策略、数据库查询优化、减少模板渲染时间等，以提高应用的运行速度。 1.12 Python兼容性 Django 1.8兼容Python的多个版本，文档列出了支持的范围，并给出了版本兼容性的注意事项。 1.13 地理框架 Django提供了地理空间支持，可以处理地理位置数据，适用于地图应用和其他需要地理位置功能的项目。 1.14 常用Web应用工具 Django文档还涵盖了诸如用户认证、中间件、缓存系统、静态文件处理等常见Web开发工具的使用方法。 1.15 其他核心功能除了上述内容，Django还有许多其他核心功能，如电子邮件发送、信号处理器、管理命令等，这些都在文档中有所阐述。 1.16 Django开源项目最后，文档介绍了Django的开源性质，鼓励用户参与项目的贡献，包括报告问题、提交补丁或开发新的应用和库。 2.1 开始使用Django 这部分提供了对Django的整体概览，以及快速安装和初步设置的指导。 2.2 至2.11 逐步教程一系列逐步教程带领用户从创建第一个Django应用开始，直至编写可重用的应用，以及如何为Django贡献代码。 3.1 至3.1 使用Django 这部分详细介绍了如何在实际项目中使用Django，包括设置、配置、部署等方面的知识。通过这份官方文档，无论是初学者还是经验丰富的开发者，都能深入理解Django的各个方面，有效地利用其功能来构建高质量的Web应用程序。

Django Documentation, Release 1.8.18.dev20161220133054

2.1.5 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’).

2.1.6 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)

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

for non-programmers to use.

10 Chapter 2. Getting started

Django Documentation, Release 1.8.18.dev20161220133054

2.1.7 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 staticfiles %}

<html>

<head>

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

</head>

<body>

{% block content %}{% endblock %}

</body>

</html>

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.

2.1. Django at a glance 11

Django Documentation, Release 1.8.18.dev20161220133054

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.

2.1.8 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!

2.2 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.

2.2.1 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/download/ 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.3.3 (default, Nov 26 2013, 13:33:18)

[GCC 4.8.2] on linux

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

>>>

2.2.2 Set up a database

This step is only necessary if you’d like to work with a “large” database engine like PostgreSQL, MySQL, or Oracle.

To install such a database, consult the database installation information.

12 Chapter 2. Getting started

Django Documentation, Release 1.8.18.dev20161220133054

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

following command:

$ python -c "import django; print(django.get_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.8 and Python 3.2 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.

2.3.1 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/

__init__.py

settings.py

urls.py

wsgi.py

14 Chapter 2. Getting started

剩余1608页未读，继续阅读

happy_ken6688

粉丝: 2
资源: 10

Django 1.8 官方文档精要

Django 1.8 官方文档详解

Django 1.8 官方文档速览

Django 1.8官方文档：入门与核心功能详解

Django1.8官方文档（中文版）

django1.8官方离线文档

django 1.8 官方英文文档

django1.8中文文档

精通Django 1.8中文文档

Django 1.8 英文文档速览

Django 1.8官方英文文档详解：入门与核心功能

最新资源