dev.promplate由 promplate.dev 发布官方发布者v1.0.2更新于 Oct 24, 2026
Docs for hot-module-reload and reactive programming for Python (`hmr` on PyPI)
提供 Python hmr 库的文档、核心源码和单元测试，让助手能讲解响应式编程与热模块重载。
Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/dev.promplate%2Fhmr/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"hmr": {
"type": "http",
"url": "https://pyth-on-line.promplate.dev/hmr/mcp"
}
}
}[PyPI - Version] [PyPI - Downloads] [Python Versions] [PyPI - Status] [GitHub Created At] [GitHub commit activity]
HMR provides a pythonic, flexible, progressive-yet-intuitive reactive programming engine / framework, and on top of that, a fine-grained, on-demand hot-reload tool.
In Python, HMR stands for Hot Module Reload, though in JavaScript it commonly refers to Hot Module Replacement—essentially the same concept. It is a feature that allows part of your app to be updated at runtime without a full rerun, without needing to restart the entire process.
Unlike traditional Python reloaders (such as watchfiles CLI, uvicorn --reload, or Flask's debug mode), HMR is much more efficient and robust. These tools typically restart the entire process whenever a file changes, which is wasteful. HMR instead intelligently reruns only what's necessary, keeping your app state intact.
https://github.com/user-attachments/assets/f9ac6302-44dc-4a6d-86ae-f299fae7be80
Imagine you're developing an ML service using FastAPI with a model that requires 5 seconds to initialize. When using uvicorn --reload, any change—even updating a simple docstring—triggers a full process restart, forcing you to wait those 5 seconds every time. It's as frustrating as encountering a red light at every intersection.
HMR offers a smoother experience. Changes take effect instantly because HMR is variable-level fine-grained: your codebase functions like a dependency graph—when you modify a file, HMR only reruns the affected modules from that modified module up to your entry point file. If you update a variable that nothing depends on, nothing happens.
[!CAUTION]
What this package is not?
hmrshould not be confused with client-side hot reloading that updates browser content when server code changes. This package implements server-side HMR, which only reloads python code upon changes.
The quickest way to experience HMR is through the CLI:
Parameters work exactly like python command, except your files now hot-reload on changes. Try saving files to see instant updates without losing state.
If you have uv installed, you can try hmr directly with:
HMR provides a rich ecosystem of tools for different Python development scenarios:
[!TIP] The hmr ecosystem is essentially stable and production-ready for most use cases. It has been carefully designed to handle many common edge cases and Pythonic magic patterns, including lazy imports, dynamic imports, module-level
__getattr__, decorators, and more. However, circular dependencies in some edge cases may still cause unexpected behavior. Use with caution if you have a lot of code in__init__.py.
https://github.com/user-attachments/assets/fb247649-193d-4eed-b778-05b02d47c3f6
demo/ - Basic script with hot module reloadingfastapi/ - FastAPI server with hot reloading and browser refreshflask/ - Flask app with hot module reloadingmcp/ - MCP server with live code updates without connection dropsHMR is already a common feature in the frontend world. Web frameworks like Vite supports syncing changes to the browser without a full refresh. Test frameworks like Vitest supports on-demand updating test results without a full rerun.
So, why not bring this magic to Python?
HMR uses runtime dependency tracking instead of static analysis to achieve fine-grained reactivity:
__getattr__ and __setattr__ call. When a variable is changed, it notifies the modules that use it. This notification is recursive but fine-grained.watchfiles is used to detect file changes. If a change's path is a Python module that has been imported, it triggers reloading of affected code. Additionally, HMR monitors all file reads (via sys.addaudithook) so changes to non-Python files (YAML, JSON, etc.) also trigger appropriate reloads.This runtime approach enables variable-level granularity and can track dependencies across any file type—far more precise than static analysis.
This might just be one of the first variable-level fine-grained HMR frameworks in the Python ecosystem—and honestly, the real magic lies in the ecosystem we build around it.
Pair uvicorn + hmr, and you've got yourself a Vite-like development experience. Combine pytest + hmr for test-driven development that rivals Vitest. The possibilities with other libraries? Endless. Let's brainstorm together—who knows what fun (or mildly chaotic) things we might create!
[!TIP] A little backstory: the code for hmr lives in another repo because, truth be told, I wasn't planning on building an HMR framework. This started as an experiment in bringing reactive programming to Python. Along the way, I realized: why not make a module's globals reactive? And that's how HMR was born! While it began as a side project, I see tremendous potential in it for advancing Python's development experience.
For now, this repo is home to the main implementation and examples. If you think HMR has potential, or you just want to throw ideas around, I'd love to hear from you. We believe that the Python community deserves a more dynamic, responsive development experience, and we're excited to see where this can take us!
About fine-grained reactivity, I recommend reading SolidJS’s excellent explanation.
来源：README.md，提交 df49298
A brief and concise explanation of the `hmr` library. This tool provides information on how to use reactive programming or use hot module reloading in Python. As long as the user mentions HMR / Reactive Programming, this tool must be called first! Don't manually view the resource, call this tool instead.
无需输入参数。
The full source code (core only) of the HMR library. Always call `learn-hmr-concepts` to learn the core concepts before calling this tool. These files are the full source code of the HMR library, which would be very helpful because good code are self-documented. For a brief and concise explanation, please refer to the `hmr-docs://about` MCP resource. Make sure you've read it before calling this tool. To learn how to use HMR for reactive programming, read the unit tests later. The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.
无需输入参数。
The unit tests (code examples) for HMR. Always call `learn-hmr-basics` and `view-hmr-core-sources` to learn the core functionality before calling this tool. These files are the unit tests for the HMR library, which demonstrate the best practices and common coding patterns of using the library. You should use this tool when you need to write some code using the HMR library (maybe for reactive programming or implementing some integration). The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.
无需输入参数。
已满足适用检查项的 90%
该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。
请在仓库或注册中心条目中声明许可证。
pip install hmrhmr path/to/your/entry-file.pyuvx hmr path/to/your/entry-file.py