Skip to content

Conversation

eumiro
Copy link
Contributor

@eumiro eumiro commented Mar 31, 2025

Format cross-references and make the example code more explicit.

BTW, do you prefer using jupyter-execute or >>>-indented docstring-like code?

@coveralls
Copy link

Pull Request Test Coverage Report for Build 14178685124

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 95.33%

Totals Coverage Status
Change from base Build 14160792499: 0.0%
Covered Lines: 18495
Relevant Lines: 19401

💛 - Coveralls

Copy link
Collaborator

@IvanIsCoding IvanIsCoding left a comment

Choose a reason for hiding this comment

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

With regards to jupyter-execute. For code that has plots (i.e. generators, graph layouts) we always want to use the Jupyter option to generate visual output for the user.

For code that needs to run but outputs text, it is 50/50. I talked with Matthew, too many would slow down our documentation. But right now we have too few.

So in general if the method is non-trivial and the outptu is useful, jupyter-execute. But either is fine, I appreciate just the plain markdown in places where we used to have no documentation

@IvanIsCoding IvanIsCoding added this pull request to the merge queue Apr 1, 2025
Merged via the queue into Qiskit:main with commit 2b8a173 Apr 1, 2025
31 checks passed
@eumiro eumiro deleted the docs-toposort branch April 1, 2025 17:24
SILIZ4 pushed a commit to SILIZ4/rustworkx that referenced this pull request Jul 4, 2025
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.

3 participants