GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • FlyPython
  • Courses
  • Tracks
  • Leaderboard
  • Learn
  • Radar
  • Pricing
  • 中文
  • Sign in
  • Examples
  • Resources
  • Badges
  • Search
  • Help

This view

  • Original page
  • New address

GeezerVison is showing flypython.com — Learn practical Python — FlyPython

Ordered learning path

01
Beginner

Build a dependable Python foundation

Create an isolated project, make one function contract explicit, and turn a useful script into a product you can change safely.

Read: Build a dependable Python foundation with tests →

More in this path:Build a Python product that can be changed safely →Modern Python typing in practice: Protocol, TypedDict, and PEP 695 →Decide whether to adopt free-threaded Python (3.15, no-GIL) →Adopt the uv workflow for Python projects →

02
Beginner

Define an HTTP boundary

Specify one endpoint, validate at the boundary, bound its dependencies, and write the test and release-evidence checklist.

Read: Design a small Python web API with explicit boundaries →

03
Intermediate

Design a retryable workflow run

Write a run contract that makes repeated work observable, idempotent, safe to resume, and strict about business completion.

Read: Design a retryable Python automation run →

More in this path:Reliable async Python patterns and pitfalls →

04
Intermediate starting point

Add an agent only where judgment is needed

Run the deterministic example, keep validation, tools, and deadlines outside the model, and apply the same discipline to coding agents.

Read: Build a testable Python agent loop without an API key →

More in this path:Migrate a Python MCP server to the 2026-07-28 specification →Use Python well with AI coding →Context budgeting and bounded tasks for coding agents →Give every coding agent one AGENTS.md source of truth (AGENTS.md tutorial) →Build LLM prompts with Python template strings (t-strings, PEP 750) →

Put a path to work

Complete one playbook and keep the output.

The resource page turns each path into a checklist with a named artifact, and every runnable example has a one-command verifier. New and updated guides are also available through RSS →

Choose a playbookRun an example
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.