One again, as part of the research for the Flask book, I have recorded an interesting call with a developer. This time that develop was Armin Ronacher, the creator of Flask. We talked about APIs, blueprints, and more. See below the video for a full table of contents.
Note to those viewing this via email or Planet Python: I noticed that the embedded YouTube video doesn’t show up for you. Click through to the article to view it.
Thanks again to Rod Montgomery for the table of contents:
00:00 Geeks have an awkward moment
00:40 What did you do before Flask?
01:35 What was the impetus for Flask/Jinja/Werkzeug?
03:10 Released 0.10; should we use Python3 now? Maybe not just yet…
06:12 How are Blueprints supposed to be used?
09:10 Best practices for configuration
12:58 Adv pattern example: custom exception handler
15:35 “I’m a lousy tester” Signals and Blinker
17:30 “Don’t have a testing solution that makes me happy, so don’t want to put it in the docs.”
18:30 TDD creates horrible APIs, so not a fan
19:11 More about Blinker/Signals
20:58 Make docs look nice, write an overview, then detailed API docs from docstrings
25:20 Fav Extensions: SQLAlchemy, Frozen-Flask
28:25 Tools for Debugging
30:00 Error reporting: Sentry as error dashbaord
31:30 API setup? APIs defined by semantics
36:33 Fireteam uses Python
37:55 Feedback is welcome, wrapup and thanks