Django 1.9官方文档：入门指南与核心概念详解

5星 · 超过95%的资源需积分: 15 20 浏览量更新于2024-07-21 1 收藏 5.85MB PDF 举报

Django 1.9官方文档是Django软件基金会发布的一份全面指南，该版本于2016年2月6日更新。Django作为一款功能强大的Web框架，旨在帮助开发者轻松构建高质量的动态网站。这份文档为用户提供了一系列详尽的资源，无论你是初学者还是有经验的开发者，都能从中找到所需的信息。 1. 获取帮助：针对新手或遇到问题的用户，文档提供了多种求助途径：首先推荐查看常见问题解答（FAQ），通常能找到许多解决方案；如果需要特定主题的信息，可以查阅概览索引、模块索引或详细目录，以便快速定位；邮件列表（django-users）的归档搜索也是一个不错的资源，你可能在其中找到类似问题的答案；此外，利用IRC频道#django进行实时交流，或者查阅过去的聊天记录，也可能找到你需要的信息。如果你发现bug，可以通过官方的票务跟踪系统报告。 2. 文档组织： Django文档结构清晰，便于查找和学习。它分为几个主要部分： - 教程：这是引导新用户入门的起点，通过一系列逐步操作指导你创建一个Web应用，适合完全没有经验的人。 - 话题指南：这些指南深入讨论了关键的主题和概念，提供高级别的概述，同时提供有用的背景知识和详细解释，有助于加深理解。 - 参考指南：这部分包含技术性的细节和API文档，是开发过程中查阅具体函数、类和设置的宝库，对于编写代码和解决复杂问题至关重要。 3. 版本更新：文档针对的是1.9.3.dev20160206142456版本，这意味着它反映了当时的最新特性和技术，随着时间的推移，可能会有后续版本的更新和补充。 Django 1.9官方文档是开发者的必备工具，它不仅包括从零开始搭建项目的教程，还有深入浅出的话题指南和详尽的API参考，无论你是想要学习Django还是解决实际开发中的问题，都能在这个文档中找到答案。同时，文档还强调了社区支持的重要性，鼓励用户参与交流和贡献，共同提升整个框架的质量。

Django Documentation, Release 1.9.3.dev20160206142456

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.4.x

[GCC 4.x] 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.9.3.dev20160206142456

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

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

Django Documentation, Release 1.9.3.dev20160206142456

These ﬁles are:

• The outer mysite/ root directory is just a container for your project. Its name doesn’t matter to Django; you

can rename it to anything you like.

• manage.py: A command-line utility that lets you interact with this Django project in various ways. You can

read all the details about manage.py in django-admin and manage.py.

• The inner mysite/ directory is the actual Python package for your project. Its name is the Python package

name you’ll need to use to import anything inside it (e.g. mysite.urls).

• mysite/__init__.py: An empty ﬁle that tells Python that this directory should be considered a Python

package. (Read more about packages in the ofﬁcial Python docs if you’re a Python beginner.)

• mysite/settings.py: Settings/conﬁguration for this Django project. Django settings will tell you all

about how settings work.

• mysite/urls.py: The URL declarations for this Django project; a “table of contents” of your Django-

powered site. You can read more about URLs in URL dispatcher.

• mysite/wsgi.py: An entry-point for WSGI-compatible web servers to serve your project. See How to

deploy with WSGI for more details.

2.3.2 The development server

Let’s verify your Django project works. Change into the outer mysite directory, if you haven’t already, and run the

following commands:

$ python manage.py runserver

You’ll see the following output on the command line:

Performing system checks...

System check identified no issues (0 silenced).

You have unapplied migrations; your app may not work properly until they are applied.

Run `python manage.py migrate' to apply them.

February 06, 2016 - 15:50:53

Django version 1.9, using settings `mysite.settings'

Starting development server at http://127.0.0.1:8000/

Quit the server with CONTROL-C.

Note: Ignore the warning about unapplied database migrations for now; we’ll deal with the database shortly.

You’ve started the Django development server, a lightweight Web server written purely in Python. We’ve included this

with Django so you can develop things rapidly, without having to deal with conﬁguring a production server – such as

Apache – until you’re ready for production.

Now’s a good time to note: don’t use this server in anything resembling a production environment. It’s intended only

for use while developing. (We’re in the business of making Web frameworks, not Web servers.)

Now that the server’s running, visit http://127.0.0.1:8000/ with your Web browser. You’ll see a “Welcome to Django”

page, in pleasant, light-blue pastel. It worked!

Changing the port

2.3. Writing your ﬁrst Django app, part 1 15

Django Documentation, Release 1.9.3.dev20160206142456

By default, the runserver command starts the development server on the internal IP at port 8000.

If you want to change the server’s port, pass it as a command-line argument. For instance, this command starts the

server on port 8080:

$ python manage.py runserver 8080

If you want to change the server’s IP, pass it along with the port. So to listen on all public IPs (useful if you want to

show off your work on other computers on your network), use:

$ python manage.py runserver 0.0.0.0:8000

Full docs for the development server can be found in the runserver reference.

Automatic reloading of runserver

The development server automatically reloads Python code for each request as needed. You don’t need to restart the

server for code changes to take effect. However, some actions like adding ﬁles don’t trigger a restart, so you’ll have to

restart the server in these cases.

2.3.3 Creating the Polls app

Now that your environment – a “project” – is set up, you’re set to start doing work.

Each application you write in Django consists of a Python package that follows a certain convention. Django comes

with a utility that automatically generates the basic directory structure of an app, so you can focus on writing code

rather than creating directories.

Projects vs. apps

What’s the difference between a project and an app? An app is a Web application that does something – e.g., a Weblog

system, a database of public records or a simple poll app. A project is a collection of conﬁguration and apps for a

particular website. A project can contain multiple apps. An app can be in multiple projects.

Your apps can live anywhere on your Python path. In this tutorial, we’ll create our poll app right next to your

manage.py ﬁle so that it can be imported as its own top-level module, rather than a submodule of mysite.

To create your app, make sure you’re in the same directory as manage.py and type this command:

$ python manage.py startapp polls

That’ll create a directory polls, which is laid out like this:

polls/

__init__.py

admin.py

apps.py

migrations/

__init__.py

models.py

tests.py

views.py

This directory structure will house the poll application.

16 Chapter 2. Getting started

剩余1668页未读，继续阅读

Allianzcortex

粉丝: 1
资源: 2

Django 1.9官方文档：入门指南与核心概念详解

Python django框架 book中文版

django.pdf

django学习pdf

如何取消 RemovedInDjango19Warning: Model class openchannels.models.ShowRooms2 doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded. This will no longer be supported in Django 1.9. 的报错

Django报错：RemovedInDjango19Warning: Model class openchannels.models.Channels doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded. This will no longer be supported in Django 1.9.

django4.0中文文档

ModuleNotFoundError: No module named 'django.forms.util'

django3.1中文文档html版下载

django drf接口文档

<li {% ifequal 不能使用

最新资源