格林伯格的Flask Web开发全书

5星 · 超过95%的资源需积分: 10 149 浏览量更新于2024-07-23 1 收藏 8.45MB PDF 举报

《Flask Web Development》是由Miguel Grinberg编著的一本权威指南，该书于2014年首次出版。这本书专为Python Web开发者设计，尤其针对Flask框架，它是作者对轻量级Web应用开发的一种简洁而高效的方法。Grinberg以其深入浅出的风格，为读者提供了构建现代Web应用程序所需的实用技能和理论知识。本书涵盖了Flask的核心概念，如路由、模板引擎、数据库集成、表单处理以及安全措施等，适合初学者快速入门，也适合有一定经验的开发者进一步提升他们的Flask项目能力。作为一本Nutshell Handbook系列作品，它强调了实践性和实用性，通过实例演示帮助读者掌握如何在实际项目中应用Flask。版权方面，所有权利归Miguel Grinberg所有，未经许可不可随意复制或商业使用。O'Reilly Media负责书籍的出版发行，包括纸质版和在线版本，用户可以通过访问O'Reilly Safari Online书店获取更多资源。该书的第一版于2014年4月25日发布，并持续更新修订以保持内容的最新性，用户可以查询O'Reilly的在线错误报告页面获取最新修订信息。《Flask Web Development》的编辑团队由Meghan Blanchette和Rachel Roumeliotis主导，生产编辑Nicole Shelby，以及Copyeditor Nancy Kotary、Proofreader Charles Roumeliotis等专业人员共同参与，确保了书籍的质量和一致性。封面设计由Randy Comer负责，内部设计则由David Futato操刀，插图则出自Rebecca Demarest之手。《Flask Web Development》是一本不可或缺的工具书，对于想要学习和深化理解Flask框架，或者寻求在Python 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

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

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

剩余257页未读，继续阅读

philipx41

粉丝: 0
资源: 11

格林伯格的Flask Web开发全书

Flask Web Development.pdf 最新 原版

Flask.Web.Development.2nd.Edition

2018.03 page303 (Web Development) Miguel Grinberg-Flask Web

flask web development文献

flask书籍推荐(近五年或近三年的书)

请分别生成几篇python的MySQL操作、scoket通信、flask框架、html、css、javas的参考文献，请以标准格式给出

Python App开发教程有哪些

python游戏开发参考文献

查找一篇关于网站类开发的外文文献

flask web development v2

最新资源

Flask Web Development.pdf 最新原版