updated the output to # >>

[Amanbig]

Related Issues

• fixes Standardise print outputs in code examples #11005

Proposed Changes:

Standardized the prefix used for print outputs in docstring code examples across the repository to uniformly use # >> . This fixes instances that were using inconsistent formatting (# >>> , >>> , >> , # > , and bare # ).

Files updated:

• haystack/tools/from_function.py
• haystack/core/component/sockets.py
• haystack/components/tools/tool_invoker.py
• haystack/components/generators/azure.py
• haystack/components/builders/answer_builder.py
• haystack/components/agents/state/state_utils.py
• haystack/components/converters/html.py

How did you test it?

• Visually inspected the modified files to ensure the # >> prefix is correctly applied to output snippet lines exclusively.
• Formatting runs to ensure no regressions (strictly docstring changes, no code logic was altered).

Notes for the reviewer

• Note: I deliberately left instances like # > comparator in document_store.py alone, as those serve as section headers rather than print output examples.
• Because this is purely a documentation/docstring change, a release note was omitted per the contributing guidelines.

Checklist

• I have read the contributors guidelines and the code of conduct.
• I have updated the related issue with new insights and changes.
• I have added unit tests and updated the docstrings.
• I've used one of the conventional commit types for my PR title.
• I have documented my code.
• I have added a release note file, following the contributors guidelines. (N/A - docs only)
• I have run pre-commit hooks and fixed any issue.

[vercel]

@Amanbig is attempting to deploy a commit to the deepset Team on Vercel.

A member of the Team first needs to authorize it.

[coveralls]

Pull Request Test Coverage Report for Build 23852121732

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 92.904%

---

Totals
Change from base Build 23851947089:	0.0%
Covered Lines:	15880
Relevant Lines:	17093

---

💛 - Coveralls

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
haystack-docs	Ready	Preview, Comment	Apr 1, 2026 2:02pm

[davidsbatista]

LGTM

[davidsbatista]

Looks good!