Skip to content

feat(plugins): run the Python profiler with rc profile python - #20

Merged
colinjlacy merged 1 commit into
runtimeconditions:mainfrom
itvi-1234:python-profiler-plugin
Nov 18, 2026
Merged

colinjlacy merged 1 commit into
runtimeconditions:mainfrom
itvi-1234:python-profiler-plugin

Conversation

@itvi-1234

@itvi-1234 itvi-1234 commented Nov 18, 2026 •

Copy link
Copy Markdown
Member

Add the Python profiler as an optional language add-on, found the way the others are: runtimeconditions-python-profiler on PATH, or the absolute path in RC_PYTHON_PROFILER. It is run only if its --version --json lists core profile schema 0.4.0, and everything after "python" is passed to it unchanged.

Add the Python profiler as an optional language add-on, found the way the others are:
runtimeconditions-python-profiler on PATH, or the absolute path in RC_PYTHON_PROFILER. It is run only if its
--version --json lists core profile schema 0.4.0, and everything after "python" is passed to it unchanged.

The profiler finds binding packages through the metadata of the Python environment it is installed in, so the
install hint says to install it into the workload's virtual environment, not an isolated one such as pipx makes.
Its console script starts that environment's interpreter, so rc lists no runtime for it.

Tested with a fake runner and, by hand, with the real profiler: rc plugins list shows python ready, and rc profile
python generate prints the same profile as running the profiler directly.
@colinjlacy
colinjlacy merged commit 5c03a31 into runtimeconditions:main Nov 18, 2026
4 checks passed
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.

2 participants