Book Image

Python Web Development with Sanic

By : Adam Hopkins
Book Image

Python Web Development with Sanic

By: Adam Hopkins

Overview of this book

Today’s developers need something more powerful and customizable when it comes to web app development. They require effective tools to build something unique to meet their specific needs, and not simply glue a bunch of things together built by others. This is where Sanic comes into the picture. Built to be unopinionated and scalable, Sanic is a next-generation Python framework and server tuned for high performance. This Sanic guide starts by helping you understand Sanic’s purpose, significance, and use cases. You’ll learn how to spot different issues when building web applications, and how to choose, create, and adapt the right solution to meet your requirements. As you progress, you’ll understand how to use listeners, middleware, and background tasks to customize your application. The book will also take you through real-world examples, so you will walk away with practical knowledge and not just code snippets. By the end of this web development book, you’ll have gained the knowledge you need to design, build, and deploy high-performance, scalable, and maintainable web applications with the Sanic framework.
Table of Contents (16 chapters)
Part 1:Getting Started with Sanic
Part 2:Hands-On Sanic
Part 3:Putting It All together

Running our application

Now that we have laid our application foundations, we are almost ready to run our server. We are going to make one small change to to include a small little utility to run at startup to show us what routes are registered:

from .utilities.app_factory import create_app
from sanic.log import logger
app = create_app()
def display_routes(app, _):"Registered routes:")
    for route in app.router.routes:"> /{route.path}")

You can head over to the GitHub repository,, to see the full source code.

We can now start our application for the first time. Remember, this is going to be our pattern:

$ sanic src.server:app -p 7777 --debug --workers=2

We should see something like this:

[2021-05-30 11...