Make PyQuilExecutableResponse as opaque as BinaryExecutableResponse
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 358
- Avg merge
- 1d 58m
- Merged PRs (30d)
- 4
Description
users are able to poke and prod at PyQuilExectuableResponse in ways that do not work with BinaryExecutableResponse which makes QVM -> QPU transition not as smooth
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the PyQuilExecutableResponse and BinaryExecutableResponse implementations and compare the public behavior exposed by each. Check how QVM and QPU responses use these classes, then define completion by making PyQuilExecutableResponse no more inspectable or manipulable than BinaryExecutableResponse while preserving the QVM-to-QPU transition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100