Django 3.1.6.dev 文档：入门与深入指南

版权申诉

82 浏览量更新于2024-07-21 收藏 6.89MB PDF 举报

"这是Django软件基金会发布的Django官方文档，版本为3.1.6.dev，日期为2021年1月29日。文档涵盖了Django框架的基础到高级内容，旨在帮助开发者全面理解并掌握Django的使用。" 在Django 3.1.6.dev版本的文档中，主要包含以下几个核心知识点： 1. **模型(Model)层**：这是Django的数据层，用于定义数据库结构。开发者可以通过创建Python类来定义模型，这些类映射到数据库表，并提供操作数据的方法。 2. **视图(View)层**：视图是处理用户请求并返回响应的部分。它们负责获取数据、处理逻辑，并返回合适的HTTP响应。视图通常与模板一起工作，提供动态内容。 3. **模板(Template)层**：Django的模板系统允许开发者使用一种简洁的语法来描述HTML页面，其中可以嵌入变量和控制结构，实现动态渲染。 4. **表单.Forms**：Django提供了处理用户输入数据的表单系统，包括验证、渲染HTML表单以及从POST数据中提取数据。 5. **开发过程(The development process)**：文档会介绍如何设置开发环境，如何进行版本控制，以及Django项目的基本开发流程。 6. **管理界面(The admin)**：Django的内置管理界面是一个强大的工具，允许管理员轻松地添加、更改和删除模型实例，无需编写额外的代码。 7. **安全(Security)**：这部分会讲解如何确保Django应用的安全，包括防止常见的Web攻击，如跨站脚本(XSS)和跨站请求伪造(CSRF)。 8. **国际化(Internationalization)和本地化(Localization)**：Django支持多语言，这部分介绍如何使应用适应不同的语言和文化环境。 9. **性能和优化(Performance and optimization)**：文档会提供提高Django应用性能的技巧和建议，包括数据库查询优化、缓存机制等。 10. **地理框架(Geographic framework)**：Django包含对地理位置数据的支持，如GIS功能，用于处理地图和坐标数据。 11. **常见Web应用工具(Common Web application tools)**：Django提供了许多用于构建Web应用的工具和库，如中间件、URL路由系统等。 12. **其他核心功能(Other core functionalities)**：这部分可能涵盖Django的其他特性，如电子邮件支持、用户认证系统等。 13. **Django开源项目(The Django open-source project)**：文档会介绍Django的社区、贡献方式，以及如何参与Django的开发。此外，文档还提供了快速入门指南，从安装Django到编写第一个Django应用的详细教程，分为多个部分，逐步引导开发者实践。对于希望深入学习Django的开发者，还有高级教程和如何为Django贡献代码的指南。这是一份非常全面且深入的参考资料，无论你是初学者还是经验丰富的开发者，都能从中获益。

Django Documentation, Release 3.1.6.dev

Listing 3: mysite/news/admin.py

from django.contrib import admin

from . import models

admin.site.register(models.Article)

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

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 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:

Listing 4: mysite/news/urls.py

from django.urls import path

from . import views

urlpatterns = [

path('articles/<int:year>/', views.year_archive),

path('articles/<int:year>/<int:month>/', views.month_archive),

path('articles/<int:year>/<int:month>/<int:pk>/', views.article_detail),

]

The code above maps URL paths to Python callback functions (“views”). The path strings use parameter tags to

“capture” values from the URLs. When a user requests a page, Django runs through each path, 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 paths are compiled into regular expressions at load time.

Once one of the URL patterns matches, Django calls the given view, which is a Python function. Each view gets

passed a request object – which contains request metadata – and the values captured in the pattern.

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

article_detail(request, year=2005, month=5, pk=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:

10 Chapter 2. Getting started

Django Documentation, Release 3.1.6.dev

Listing 5: 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.

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:

Listing 6: 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:

2.1. Django at a glance 11

Django Documentation, Release 3.1.6.dev

Listing 7: mysite/templates/base.html

{% load static %}

<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 means that a site redesign can be done by 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 by only 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 lets you create RSS and Atom feeds by writing a small Python class.

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

The next 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 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/downloads/ or with your operating system’s package man-

ager.

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

12 Chapter 2. Getting started

Django Documentation, Release 3.1.6.dev

• 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 3.1, which supports Python 3.6 and 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’re using an older version of Python, check What Python version

can I use with Django? to ﬁnd a compatible version of Django.

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 head over to the Getting Help section of the FAQ.

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/

(continues on next page)

14 Chapter 2. Getting started

剩余2040页未读，继续阅读

ztenv

粉丝: 5w+
资源: 27

Django 3.1.6.dev 文档：入门与深入指南

轻量级Django.pdf

from-python-to-django.pdf

django.pdf 1.11.9

Learning Website Development with Django.pdf

Flash+gunicorn+django.pdf

Python Web Development with Django.pdf

web programming in python with Django.pdf

Web Development with Python and Django.pdf

ta-lib-0.5.1-cp312-cp312-win32.whl

在线实时的斗兽棋游戏，时间赶，粗暴的使用jQuery + websoket 实现实时H5对战游戏 + java.zip课程设计

最新资源