Replies: 1 comment
-
|
What would be the use case for Thanks for sharing your idea! To make sure I understand correctly, are you thinking of a CLI tool that lets people interact with Qiskit without writing Python? For example, loading QASM files, submitting them to a backend, or printing circuits directly in the terminal The main challenge I see is scope: Qiskit’s API surface is very large, so if the CLI tries to cover everything it could end up re-implementing the full SDK as command-line arguments. That might become hard to maintain and confusing for users. If your interest is more in a focused workflow (like loading, visualizing, and submitting QASM, or handling a subset of circuit operations), that might make for a cleaner project. Clarifying which use cases you want to prioritize could help figure out a tool on top of existing tools. Specially in the context of QAMP 2025 :) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Supp... this is more of a question, really rather than a suggestion.
So lately I've been thinking of creating/being part of a project that involves using the Qiskit SDK in a command line interface, especially for people that do have preference to use tools in a terminal. Now this got me thinking, is this an idea that really makes sense to try out and implement, and are you guys at Qiskit currently working on something of that sort, which I might help contribute to?
Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions