Jake Lishman

Results 50 issues of Jake Lishman

### Summary I have recently seen several users struggle to install a complete version of Graphviz upon seeing the `MissingOptionalLibraryError` message. This updates the message to make it clearer that...

documentation
Changelog: None

### Summary I was pretty surprised to see that we had very little written for our principal module, and the first entry in our API docs. This is a totally...

documentation
Changelog: None
mod: circuit

### Summary In the control-flow builders, there are typically two ways the individual blocks can be reconstructed to be unified over the qubit and clbit resources. We generally attempt to...

Changelog: None
mod: circuit

### What should we add? ## Summary Qiskit's OpenQASM export needs a way for us to define what header files the file is defined in terms of, including letting the...

type: discussion
mod: qasm2
mod: qasm3

QPY needs to add support for the additional variable-tracking that `QuantumCircuit` will support after #10924, including reconstructing the `Var` instances and correctly determining which are inputs, regular variables and closures...

mod: qpy

### Summary This necessitates adding some extra definitions to the circuit header. When standalone variables are used, we do not re-encode the entire variable (which would take a miniumum of...

on hold
Changelog: New Feature
mod: qpy

### What is the expected enhancement? My understanding is that `stdgates.inc` was intended to be a true portable standard library of the language (at least as far as implementers of...

enhancement

We have identified a few obvious discrepancies between the current version of the arXiv paper and the state of this live specification. Since we anticipate making a new version of...

paper

From the TSC meeting 2022-10-28: we should consider moving the source of the arXiv paper specification of OpenQASM 3 into this repository, especially if there are changes to be made...

paper

`jupyter_client` version is 7.4.8 pyzmq 25 released earlier today, which seems to have removed some old code and caused a (very old) deprecation warning to begin getting emitted on import...