Python Flask微框架开发指南：源代码深度解析

需积分: 0 54 浏览量更新于2024-07-18 收藏 8.4MB PDF 举报

《Flask Web Development》是一本由Miguel Grinberg编写的权威指南，适合那些想要学习Python Flask Web开发的读者。Flask作为一款轻量级的框架，在小型项目中表现出色，其代码结构简洁，易于理解和掌握。本书主要关注于如何利用Flask构建Web应用程序，包括设置基础环境、路由与视图、模板引擎、数据库集成以及高级主题如安全性和部署。在学习过程中，读者可以参考在线资源www.it-ebooks.info获取进一步的学习材料和实践项目。本书版权由Miguel Grinberg持有，所有权利受到保护，印制地在美国。O'Reilly Media出版了这本书，提供纸质版和电子版两种形式，教育、商业或销售推广用途均可购买。对于更多购买信息，可以通过电话或电子邮件联系O'Reilly公司的销售部门。该书由Meghan Blanchette和Rachel Roumeliotis编辑，生产编辑Nicole Shelby，以及Copyeditor Nancy Kotary、Proofreader Charles Roumeliotis等专业人员负责内容的质量把控。封面设计由Randy Comer操刀，内部设计由David Futato完成，插图则出自Rebecca Demarest之手。本书的第一版发布于2014年4月25日，并且提供了详细的修订历史，可以在O'Reilly网站上查询错误和更新详情。《Flask Web Development》是一本实用的手册，适合初学者通过清晰的步骤和实例学习Flask的核心概念，同时也为有一定经验的开发者提供了深入理解和扩展Flask应用的宝贵资源。无论是从零开始构建Web应用，还是寻求对现有项目进行Flask技术的引入，这本书都是不可或缺的参考资料。通过阅读这本书，读者将能建立起坚实的Flask基础，为构建高效、灵活的Web应用打下坚实的基础。

The git clone command installs the source code from GitHub into a flasky folder that

is created in the current directory. This folder does not contain just source code; a copy

of the Git repository with the entire history of changes made to the application is also

included.

In the first chapter you will be asked to check out the initial release of the application,

and then, at the proper places you will be instructed to move forward in the history.

The Git command that lets you move through the change history is git checkout. Here

is an example:

$ git checkout 1a

The 1a referenced in the command is a tag, a named point in the history of the project.

This repository is tagged according to the chapters of the book, so the 1a tag used in

the example sets the application files to the initial version used in Chapter 1. Most

chapters have more than one tag associated with them, so, for example, tags 5a, 5b, and

so on are incremental versions presented in Chapter 5.

In addition to checking out the source files for a version of the application, you may

need to perform some setup. For example, in some cases you will need to install addi‐

tional Python packages or apply updates to the database. You will be told when these

are necessary.

You will normally not modify the source files of the application, but if you do, then Git

will not let you check out a different revision, as that would cause your local changes to

be lost. Before you can check out a different revision, you will need to revert the files to

their original state. The easiest way to do this is with the git reset command:

$ git reset --hard

This command will destroy your local changes, so you should save anything you don’t

want to lose before you use this command.

From time to time, you may want to refresh your local repository from the one on

GitHub, where bug fixes and improvements may have been applied. The commands

that achieve this are:

$ git fetch --all

$ git fetch --tags

$ git reset --hard origin/master

The git fetch commands are used to update the commit history and the tags in your

local repository from the remote one on GitHub, but none of this affects the actual

source files, which are updated with the git reset command that follows. Once again,

be aware that any time git reset is used you will lose any local changes you have made.

Another useful operation is to view all the differences between two versions of the

application. This can be very useful to understand a change in detail. From the command

xiv | Preface

www.it-ebooks.info

line, the git diff command can do this. For example, to see the difference between

revisions 2a and 2b, use:

$ git diff 2a 2b

The differences are shown as a patch, which is not a very intuitive format to review

changes if you are not used to working with patch files. You may find that the graphical

comparisons shown by GitHub are much easier to read. For example, the differences

between revisions 2a and 2b can be viewed on GitHub at https://github.com/miguelgrin

berg/flasky/compare/2a...2b

Using Code Examples

This book is here to help you get your job done. In general, if example code is offered

with this book, you may use it in your programs and documentation. You do not need

to contact us for permission unless you’re reproducing a significant portion of the code.

For example, writing a program that uses several chunks of code from this book does

not require permission. Selling or distributing a CD-ROM of examples from O’Reilly

books does require permission. Answering a question by citing this book and quoting

example code does not require permission. Incorporating a significant amount of ex‐

ample code from this book into your product’s documentation does require permission.

We appreciate, but do not require, attribution. An attribution usually includes the title,

author, publisher, and ISBN. For example: “Flask Web Development by Miguel Grinberg

If you feel your use of code examples falls outside fair use or the permission given above,

feel free to contact us at permissions@oreilly.com.

Conventions Used in This Book

The following typographical conventions are used in this book:

Italic

Indicates new terms, URLs, email addresses, filenames, and file extensions.

Constant width

Used for program listings, as well as within paragraphs to refer to program elements

such as variable or function names, databases, data types, environment variables,

statements, and keywords.

Constant width bold

Shows commands or other text that should be typed literally by the user.

Preface | xv

www.it-ebooks.info

How to Contact Us

Please address comments and questions concerning this book to the publisher:

O’Reilly Media, Inc.

1005 Gravenstein Highway North

Sebastopol, CA 95472

800-998-9938 (in the United States or Canada)

707-829-0515 (international or local)

707-829-0104 (fax)

We have a web page for this book, where we list errata, examples, and any additional

information. You can access this page at http://www.bit.ly/flask-web-dev.

To comment or ask technical questions about this book, send email to bookques

tions@oreilly.com.

For more information about our books, courses, conferences, and news, see our website

at http://www.oreilly.com.

Find us on Facebook: http://facebook.com/oreilly

Watch us on YouTube: http://www.youtube.com/oreillymedia

Acknowledgments

I could not have written this book alone. I have received a lot of help from family, co-

workers, old friends, and new friends I’ve made along the way.

I’d like to thank Brendan Kohler for his detailed technical review and for his help in

giving shape to the chapter on Application Programming Interfaces. I’m also in debt to

David Baumgold, Todd Brunhoff, Cecil Rock, and Matthew Hugues, who reviewed the

manuscript at different stages of completion and gave me very useful advice regarding

what to cover and how to organize the material.

Writing the code examples for this book was a considerable effort. I appreciate the help

of Daniel Hofmann, who did a thorough code review of the application and pointed out

several improvements. I’m also thankful to my teenage son, Dylan Grinberg, who sus‐

pended his Minecraft addiction for a few weekends and helped me test the code under

several platforms.

O’Reilly has a wonderful program called Early Release that allows impatient readers to

have access to books while they are being written. Some of my Early Release readers

went the extra mile and engaged in useful conversations regarding their experience

working through the book, leading to significant improvements. I’d like to acknowledge

Preface | xvii

www.it-ebooks.info

剩余257页未读，继续阅读

u011728758

粉丝: 1
资源: 1

Python Flask微框架开发指南：源代码深度解析

Flash Development

Real-World Flash Game Development

Flash Game Development by Example

Flash Game Development

flash game development by example源码

Flash Development for Android Cookbook

web_development_2

Rich Web Application Development Tool-开源

The Essential Guide to Open Source Flash Development

Web-Development:维护该存储库以使我的Web开发学习代码

最新资源