Book Image

Python 3 Web Development Beginner's Guide

By : Michel Anders
Book Image

Python 3 Web Development Beginner's Guide

By: Michel Anders

Overview of this book

<p>Building your own Python web applications provides you with the opportunity to have great functionality, with no restrictions. However, creating web applications with Python is not straightforward. Coupled with learning a new skill of developing web applications, you would normally have to learn how to work with a framework as well.</p> <p><em>Python 3 Web Development Beginner's Guide</em> shows you how to independently build your own web application that is easy to use, performs smoothly, and is themed to your taste – all without having to learn another web framework.</p> <p>Web development can take time and is often fiddly to get right. This book will show you how to design and implement a complex program from start to finish. Each chapter looks at a different type of web application, meaning that you will learn about a wide variety of features and how to add them to your custom web application. You will also learn to implement jQuery into your web application to give it extra functionality. By using the right combination of a wide range of tools, you can have a fully functional, complex web application up and running in no time.</p>
Table of Contents (19 chapters)
Python 3 Web Development Beginner's Guide
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Time for action – defining the Books database


The next step is to create a module booksdb.py that uses the entity and relation modules to construct a data model that can be used conveniently by the delivery layer (the parts of the web application that deal with providing content to the client). We therefore have to define Book, Author, and User entities as well as a BookAuthor relation and a UserBook relation.

We will also provide some functions that are bit more high-level, for example, a newbook() function that checks whether a book with a given title already exists and that only creates a new Book instance if the authors are different (presumably because they wrote a book with the same title).

Having a separate layer that models data in terms that are meaningful in the context makes it easier to understand what is going on. It also keeps the delivery layer less cluttered and therefore easier to maintain.

What just happened?

After importing the Entity and Relation class, the first thing...