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

Re-consider requiring the full qiskit package instead of its sub-elements #983

Closed
andreamari opened this issue Oct 11, 2021 · 5 comments
Closed
Labels
infrastructure For issues related to building, packaging, and continuous integration.

Comments

@andreamari
Copy link
Member

Some motivations for requiring the full qiskit package instead of individual elements are:

@andreamari andreamari added infrastructure For issues related to building, packaging, and continuous integration. discussion labels Oct 11, 2021
@nathanshammah
Copy link
Member

To me it sounds fine given your comments.

@trbromley
Copy link
Contributor

We have a similar issue (PennyLaneAI/pennylane-qiskit#149) in the PennyLane-Qiskit plugin, but there suggesting the alternative approach of relying on the sub-packages rather than full qiskit.

@andreamari
Copy link
Member Author

This idea is having a Rabi oscillation between Mitiq and PL 😄

@github-actions
Copy link

This issue had no activity for 2 months, and will be closed in one week unless there is new activity. Cheers!

@github-actions github-actions bot added the stale label Dec 12, 2021
@andreamari
Copy link
Member Author

This was closed by #993

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure For issues related to building, packaging, and continuous integration.
Projects
None yet
Development

No branches or pull requests

4 participants