-
Notifications
You must be signed in to change notification settings - Fork 18
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
Get cirq-core only #94
Conversation
Codecov Report
@@ Coverage Diff @@
## master #94 +/- ##
=======================================
Coverage 99.23% 99.23%
=======================================
Files 8 8
Lines 391 391
=======================================
Hits 388 388
Misses 3 3 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting that the naming changed, Should we pin it to the latest (0.13.x)?
Rather than a naming change, this pulls in only Cirq core. When hitting
along with further dependencies (e.g., As for pinning, it's okay as is, we'd pin for |
* pre release version bump * Update CHANGELOG.md * Update pennylane_cirq/_version.py * Update pennylane_cirq/_version.py * Update pennylane_cirq/_version.py * changelog for #94 * changelog * changelog Co-authored-by: Jaybsoni <Jaybsoni@users.noreply.github.com> Co-authored-by: Jay Soni <jbsoni@uwaterloo.ca> Co-authored-by: antalszava <antalszava@gmail.com>
Installing
cirq
pulls in packages that are not used by this plugin, but packages that bring further dependency constraints.Pulling
cirq-core
only along withcirq-pasqal
should provide a solution.This is useful for the QML repository, where a dependency conflict arises between
cirq-rigetti
and TensorFlow:With the changes here, we'll no longer be requiring
cirq-rigetti
.