Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update DAGCircuit.draw() docstring with current requirements (backport #11337) #11338

Merged
merged 1 commit into from
Nov 29, 2023

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Nov 29, 2023

This is an automatic backport of pull request #11337 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

* Update DAGCircuit.draw() docstring with current requirements

Since #8162 the dag drawer hasn't required pydot to run. It now uses
rustworkx's graphviz_draw() function which directly calls graphviz.
However, in #8162 the docstring for the DAGCircuit.draw() method was not
updated to reflect this and the method documentation still said that
pydot was required. This commit fixes this oversight and updates the
docstring to correctly state that only graphviz is required (as
rustworkx is a hard dependency for Qiskit it's not anything that needs
to be documented). It also includes more details on how to install
graphviz as this is often a potential source of confusion for users.

* Update qiskit/dagcircuit/dagcircuit.py

Co-authored-by: Jake Lishman <jake@binhbar.com>

---------

Co-authored-by: Jake Lishman <jake@binhbar.com>
(cherry picked from commit c3a7d40)
@mergify mergify bot requested a review from a team as a code owner November 29, 2023 04:39
@qiskit-bot
Copy link
Collaborator

Thank you for opening a new pull request.

Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient.

While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone.

One or more of the the following people are requested to review this:

  • @Qiskit/terra-core

@github-actions github-actions bot added documentation Something is not clear or an error documentation Changelog: None Do not include in changelog labels Nov 29, 2023
@coveralls
Copy link

Pull Request Test Coverage Report for Build 7028096303

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 2 unchanged lines in 1 file lost coverage.
  • Overall coverage increased (+0.02%) to 86.935%

Files with Coverage Reduction New Missed Lines %
crates/qasm2/src/lex.rs 2 92.17%
Totals Coverage Status
Change from base Build 7025398566: 0.02%
Covered Lines: 74191
Relevant Lines: 85341

💛 - Coveralls

@jakelishman jakelishman added this pull request to the merge queue Nov 29, 2023
Merged via the queue into stable/0.45 with commit 4ee4481 Nov 29, 2023
16 checks passed
@mergify mergify bot deleted the mergify/bp/stable/0.45/pr-11337 branch November 29, 2023 11:11
@jakelishman jakelishman added this to the 0.45.2 milestone Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Changelog: None Do not include in changelog documentation Something is not clear or an error documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants