Our mission
Python remains one of the most useful ways to turn an idea into working software. AI changes how code is produced, but it makes judgment, verification, and system boundaries more important. FlyPython helps the people who now own AI-written Python — scripts, APIs, and automations — take those projects from “it runs” to “it ships”, and helps developers learn those durable skills while using modern tools.
Coach P / 小P老师
Coach P is an AI teaching style in our Skill and course files. It runs inside your own coding agent, using your model. It asks what you tried, offers a small hint, and explains named failing tests. It is not a human teacher or a certification, and does not promise learning or career outcomes.
FlyPython does not run this model or receive the chat conversation through the course workflow. Course-file requests, account authorization and submitted claim evidence are separate API data covered by our Privacy Policy. Your agent and model provider have their own data policies.
小P老师是写在 Skill 与课程文件里的 AI 教学方式，运行在你自己的 Agent 中、使用你自己的模型。先问你试过什么，再给小提示，解释具名失败测试。它不是真人教师，不代表资格认证，也不承诺学习或职业结果。FlyPython 不运行这个模型，本课程流程不会上传聊天内容；取课、账号授权和认领证据属于另行处理的 API 数据，Agent 与模型提供方也有各自的数据政策。
Who maintains this site
FlyPython is maintained through the public flypythoncom GitHub organization. Version 0.0.3 uses FlyPython as an organizational byline; it does not imply an individual author profile that has not been approved for publication.
Guides publish their source links, supported environment, last-updated date, and either a runnable verification command or a named documentation-review environment and date.
The open resource repository
The public flypythoncom/python repository is a broad, community-visible collection covering Python learning, AI agent frameworks, automation, data, web development, books, courses, and tooling.
This website is a separate editorial layer, not a synchronized subset of the repository. It can add, update, or omit links; every listed reference carries a short rationale and a public last-checked date.
Publishing standards
- Prefer primary documentation and maintainers' sources.
- Explain why a resource is useful instead of adding links for volume.
- Show update or last-checked dates and supported environments where they matter.
- For guides marked code verified, publish the runnable command and describe the tested failure paths.
- State verification consistently: name the environment (interpreter, platform, network needs), the exact command for code verification or the documentation reviewed for editorial verification, and an ISO review date — and never claim a test count without a command that reproduces it.
- Describe runnable examples in the same terms the repository content manifest records; the two are reconciled automatically in CI.
- Courses teach from files an agent reads: each folder names its exact tool and version, ships English and Chinese lessons together, and ends with a verify.py command that decides completion. Course pages always describe what that verification does not prove.
- Project Radar entries are human-written and dated: lifecycle status, maintenance evidence, and the ai_familiarity grade are maintainer judgments, never generated text, and each entry names when not to use the project.
- Do not publish fabricated usage counts, testimonials, or authority claims.
Languages
Learning material ships in English and Chinese together: guides, challenge courses and every checkpoint, tracks, runnable examples, Project Radar entries and tool comparisons. Each page declares its counterpart to search engines, and the Chinese editions link back to the English ones.
The account surfaces — sign-in, your roadmap, the leaderboard and billing — are English only. There is no separate Chinese edition of the whole site, and we would rather say that than put a language switch on pages that have nothing behind it.
Corrections
Found a broken resource or technical mistake? Open a website correction in the companion public FlyPython resource tracker and include the page URL, the problem, and a supporting source when possible. The website repository itself is not available as an anonymous public issue channel.
GitHub issues are public. Do not post personal or confidential information. A private contact address will be published only after delivery has been verified.