-
Notifications
You must be signed in to change notification settings - Fork 603
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 more spots that use MP.name #5076
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5076 +/- ##
==========================================
- Coverage 99.67% 99.67% -0.01%
==========================================
Files 394 394
Lines 35670 35462 -208
==========================================
- Hits 35554 35346 -208
Misses 116 116 ☔ View full report in Codecov by Sentry. |
@timmysilv I could provide some context if needed since (I think??) I originally added this. The original motivation was mostly |
@josh146 we're deprecating >>> qml.state().name
/Users/matthews/src/github.com/PennyLaneAI/pennylane/pennylane/measurements/measurements.py:196: PennyLaneDeprecationWarning: MeasurementProcess.name is deprecated, and will be removed in an upcoming release. To get the name of an observable from a measurement, use MeasurementProcess.obs.name instead
warn(
'Identity' that said, |
got it, thanks @timmysilv! |
Same as #5071 but in other places. I'm a little worried that maybe we shouldn't deprecate `MeasurementProcess.name` at all... seems like we kinda depend on it? My first thought was to just make them more correct (eg. "State", "Probs"), but I don't think any devices have those saved in their `dev.observables` so I suppose this might still be the best way forward
Same as #5071 but in other places.
I'm a little worried that maybe we shouldn't deprecate
MeasurementProcess.name
at all... seems like we kinda depend on it? My first thought was to just make them more correct (eg. "State", "Probs"), but I don't think any devices have those saved in theirdev.observables
so I suppose this might still be the best way forward