rigetti / rigetti/pyquil

Make starting the QVM and quilc more convenient

Open
#735 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

good first issue :baby:
Dominant language
Python
Stars
1.5k
Forks
358
Avg merge
1d 58m
Merged PRs (30d)
4

Description

I think we could make starting the QVM and quilc more convenient by allowing Python to spin up the subprocesses itself in just 1 command within Python. It could also check if they're already running by issuing ping requests to each, and seeing if they're alive. If they are, it can no-op.

I suppose the core command would be something like

import os
os.spawnl(os.P_DETACH, 'quilc -S')
os.spawnl(os.P_DETACH, 'qvm -S')

This would take some design work so it's not confusing, as there won't be terminal windows to show you things are chugging along anymore.

Thoughts? (CC: @notmgsk @ecp-rigetti @mpharrigan @lcapelluto)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or tests. Begin by locating pyquil’s existing QVM and quilc startup and ping entry points, then clarify the one-command API, behavior when processes are already running, and how users would observe failures before defining completion criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.