Skip to content

[sdk/python] Rename flamepy.rl module to flamepy.runner#341

Merged
k82cn merged 1 commit into
xflops:mainfrom
k82cn:rename-flamepy-rl-to-run
Feb 5, 2026
Merged

[sdk/python] Rename flamepy.rl module to flamepy.runner#341
k82cn merged 1 commit into
xflops:mainfrom
k82cn:rename-flamepy-rl-to-run

Conversation

@k82cn
Copy link
Copy Markdown
Contributor

@k82cn k82cn commented Feb 5, 2026

Summary

  • Renames the flamepy.rl module to flamepy.runner for a cleaner and more intuitive API
  • Updates all references across SDK, Rust code, tests, examples, and documentation

Changes

SDK/Python

  • Renamed sdk/python/src/flamepy/rl/sdk/python/src/flamepy/runner/
  • Updated internal imports in runpy.py, runner.py, __main__.py
  • Updated flamepy/__init__.py to export runner instead of rl

Rust

  • Updated common/src/lib.rs - changed flamepy.rl.runpy to flamepy.runner.runpy
  • Updated session_manager/src/storage/engine/sqlite.rs

Tests

  • Updated e2e/src/e2e/helpers.py
  • Updated e2e/tests/test_flmrun.py
  • Updated e2e/tests/test_runner.py

Examples

  • Updated examples/ps/main.py and README.md
  • Updated examples/pi/python/main.py

Documentation

  • Updated docs/tutorials/runner-setup.md
  • Updated docs/blogs/run-pi-with-runner.md
  • Updated design docs in docs/designs/FRE280-runner/ and docs/designs/RFE284-flmrun/

Usage

# Before
from flamepy.rl import Runner

# After
from flamepy.runner import Runner

Testing

All existing tests should pass after updating imports.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @k82cn, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request streamlines the flamepy Python SDK by changing a key module's name. This change improves the clarity and consistency of the API, making it easier for developers to understand and use. The modifications are purely cosmetic in nature, focusing on naming conventions rather than functional changes, but required a comprehensive update across the entire codebase to ensure seamless integration and continued functionality.

Highlights

  • Module Renaming: The flamepy.rl Python module has been renamed to flamepy.run to provide a more intuitive and cleaner API.
  • Widespread Reference Updates: All internal and external references to the flamepy.rl module have been updated across the SDK, Rust code, end-to-end tests, examples, and documentation to reflect the new flamepy.run name.
Changelog
  • common/src/apis.rs
    • Reordered use statements for better organization.
  • common/src/lib.rs
    • Updated the default application path from flamepy.rl.runpy to flamepy.run.runpy.
  • docs/blogs/run-pi-with-runner.md
    • Updated Python import statements in code examples from flamepy.rl to flamepy.run.
  • docs/designs/FRE280-runner/RFE280-implementation-summary.md
    • Updated Python import statements in code examples from flamepy.rl to flamepy.run.
  • docs/designs/FRE280-runner/RFE280-runner.md
    • Updated Python import statements in code examples from flamepy.rl to flamepy.run.
  • docs/designs/RFE284-flmrun/RFE284-flmrun.md
    • Updated references to flamepy.rl.runpy and flamepy.rl module in code examples and API descriptions.
  • docs/designs/RFE284-flmrun/runpy-enhancement-summary.md
    • Updated references to flamepy.rl module in code examples.
  • docs/designs/RFE284-flmrun/runpy-enhancements.md
    • Updated references to flamepy.rl module in code examples.
  • docs/tutorials/runner-setup.md
    • Updated Python import statements in code examples from flamepy.rl to flamepy.run.
  • e2e/src/e2e/helpers.py
    • Updated import statement from flamepy.rl to flamepy.run for RunnerContext and RunnerRequest.
  • e2e/tests/test_flmrun.py
    • Updated import statement from flamepy.rl to flamepy.run.
    • Replaced all instances of rl.RunnerContext and rl.RunnerRequest with run.RunnerContext and run.RunnerRequest respectively.
  • e2e/tests/test_runner.py
    • Updated import statement from flamepy.rl to flamepy.run.
    • Replaced all instances of rl.Runner and rl.ObjectFuture with run.Runner and run.ObjectFuture respectively.
  • examples/pi/python/main.py
    • Updated import statement from flamepy.rl to flamepy.run.
  • examples/ps/README.md
    • Updated references to Flame.rl.Runner to Flame.run.Runner in the documentation.
  • examples/ps/main.py
    • Updated import statement from flamepy.rl to flamepy.run.
    • Adjusted formatting for a list comprehension.
  • sdk/python/src/flamepy/init.py
    • Updated the __init__.py file to export the run submodule instead of rl.
  • sdk/python/src/flamepy/rl/init.py
    • File renamed to sdk/python/src/flamepy/run/__init__.py.
    • Updated internal comment to reflect the new module name.
  • sdk/python/src/flamepy/rl/main.py
    • File renamed to sdk/python/src/flamepy/run/__main__.py.
    • Updated internal comment to reflect the new module name.
  • sdk/python/src/flamepy/rl/runner.py
    • File renamed to sdk/python/src/flamepy/run/runner.py.
    • Updated internal import paths from flamepy.rl to flamepy.run.
    • Updated comments to reference flamepy.run.runpy service.
  • sdk/python/src/flamepy/rl/runpy.py
    • File renamed to sdk/python/src/flamepy/run/runpy.py.
    • Updated internal import paths from flamepy.rl to flamepy.run.
    • Updated comments and main entrypoint description to reflect the new module name.
    • Fixed minor formatting in a comment.
  • sdk/python/src/flamepy/rl/storage.py
    • File renamed to sdk/python/src/flamepy/run/storage.py.
  • sdk/python/src/flamepy/rl/types.py
    • File renamed to sdk/python/src/flamepy/run/types.py.
  • session_manager/src/storage/engine/sqlite.rs
    • Updated the argument for flamepy.rl.runpy to flamepy.run.runpy in test configurations.
Activity
  • The author has indicated that all existing tests should pass after these import updates, suggesting that local testing has been performed to validate the changes.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request is a comprehensive refactoring that renames the flamepy.rl module to flamepy.run for a more intuitive API. The changes span across the Python SDK, Rust code, tests, examples, and documentation, ensuring consistency throughout the project. The renaming is well-executed, and all references appear to be updated correctly. I've found one minor typo in the documentation that could be corrected for clarity.

Comment thread examples/ps/README.md Outdated
# Parameter Server Example

In AI-related distributed workloads, large amounts of data often need to be transferred between multiple worker nodes. Flame provides an object cache mechanism to facilitate the transfer of data objects between nodes. This example demonstrates the use of `Flame.rl.Runner` in a training scenario through a simple case based on the `Parameter Server` (ps-worker) pattern.
In AI-related distributed workloads, large amounts of data often need to be transferred between multiple worker nodes. Flame provides an object cache mechanism to facilitate the transfer of data objects between nodes. This example demonstrates the use of `Flame.run.Runner` in a training scenario through a simple case based on the `Parameter Server` (ps-worker) pattern.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

There's a small typo in the documentation. Flame.run.Runner should likely be flamepy.run.Runner to match the Python module path and for consistency with other parts of the documentation.

Suggested change
In AI-related distributed workloads, large amounts of data often need to be transferred between multiple worker nodes. Flame provides an object cache mechanism to facilitate the transfer of data objects between nodes. This example demonstrates the use of `Flame.run.Runner` in a training scenario through a simple case based on the `Parameter Server` (ps-worker) pattern.
In AI-related distributed workloads, large amounts of data often need to be transferred between multiple worker nodes. Flame provides an object cache mechanism to facilitate the transfer of data objects between nodes. This example demonstrates the use of `flamepy.run.Runner` in a training scenario through a simple case based on the `Parameter Server` (ps-worker) pattern.

@k82cn k82cn force-pushed the rename-flamepy-rl-to-run branch 2 times, most recently from 27e44d9 to 905bc10 Compare February 5, 2026 09:52
Rename the Runner module from flamepy.rl to flamepy.runner for a cleaner
and more intuitive API. This avoids conflict with the existing flamepy.run()
function used for running services.

This change updates all references across:
- SDK/Python source files
- Rust references in common and session_manager
- E2E tests
- Examples (ps, pi)
- Documentation (tutorials, blogs, design docs)
@k82cn k82cn force-pushed the rename-flamepy-rl-to-run branch from 905bc10 to 3d435e3 Compare February 5, 2026 10:09
@k82cn k82cn changed the title [sdk/python] Rename flamepy.rl module to flamepy.run [sdk/python] Rename flamepy.rl module to flamepy.runner Feb 5, 2026
@k82cn k82cn merged commit f1d743d into xflops:main Feb 5, 2026
5 checks passed
@k82cn k82cn deleted the rename-flamepy-rl-to-run branch February 5, 2026 10:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant