flagquantum-compiler-qsteed 0.1.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright [yyyy] [name of copyright owner]
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
@@ -0,0 +1,3 @@
1
+ include requirements-qsteed.txt
2
+ include RELEASING.md
3
+ recursive-include tests *.py
@@ -0,0 +1,122 @@
1
+ Metadata-Version: 2.4
2
+ Name: flagquantum-compiler-qsteed
3
+ Version: 0.1.0
4
+ Summary: QSteed circuit compiler plugin for FlagQuantum
5
+ License-Expression: Apache-2.0
6
+ Project-URL: Repository, https://github.com/FlagQuantum/FlagQuantum-Compiler-QSteed
7
+ Project-URL: Issues, https://github.com/FlagQuantum/FlagQuantum-Compiler-QSteed/issues
8
+ Requires-Python: <3.13,>=3.10
9
+ Description-Content-Type: text/markdown
10
+ License-File: LICENSE
11
+ Requires-Dist: flagquantum<0.3,>=0.2
12
+ Requires-Dist: qsteed==0.2.3+quafu.sqc
13
+ Provides-Extra: test
14
+ Requires-Dist: pytest>=7; extra == "test"
15
+ Dynamic: license-file
16
+
17
+ # FlagQuantum Compiler QSteed
18
+
19
+ `flagquantum-compiler-qsteed` is an independently installed circuit compiler
20
+ plugin for FlagQuantum. It translates FlagQuantum `CircuitIR` to a PyQuafu
21
+ `QuantumCircuit`, invokes QSteed's real transpiler, and translates the compiled
22
+ circuit back to `CircuitIR`.
23
+
24
+ The first release deliberately supports one closed, testable slice:
25
+
26
+ - static `h`, `x`, `rx`, `ry`, `rz`, and `cx` instructions with numeric angles;
27
+ - basis lowering to a selected subset of those gates, with topology routing on
28
+ the fixed six-gate basis;
29
+ - an optional undirected coupling map over the circuit's existing wires;
30
+ - deterministic QSteed basis lowering and SABRE routing;
31
+ - restoration of QSteed's final physical layout to FlagQuantum's logical wire
32
+ order.
33
+ - Quafu calibration targets with automatic or explicitly ordered physical
34
+ subgraph selection and a `target_qubits` result; physical identifiers never
35
+ replace logical QASM wires.
36
+
37
+ Measurements, observables, symbolic parameters, custom matrices, dynamic
38
+ operations, additional target fields, and larger physical topologies are
39
+ rejected. There is no compiler substitution or fallback. Omitting
40
+ `coupling_map` explicitly requests basis compilation without topology routing.
41
+ For a Quafu `chip_info` target, omitting `target_qubits` lets QSteed choose the
42
+ subgraph. Supplying it locks the logical-to-physical order after existence,
43
+ uniqueness, and connectivity validation; the plugin never substitutes another
44
+ mapping.
45
+
46
+ ## Installation
47
+
48
+ This release candidate requires FlagQuantum `>=0.2,<0.3` and the verified
49
+ QSteed build `0.2.3+quafu.sqc`. It is not yet a one-command PyPI installation:
50
+ FlagQuantum 0.2 and this QSteed build must be installed first. PyPI QSteed 0.2.2
51
+ is not a supported substitute. Python 3.12 was used for the release checks;
52
+ the declared Python 3.10–3.12 range still needs a full compatibility matrix.
53
+
54
+ From this repository, after installing a compatible FlagQuantum checkout:
55
+
56
+ ```bash
57
+ python -m pip install -r requirements-qsteed.txt
58
+ python -m pip install -e ".[test]"
59
+ python -m pytest -q
60
+ ```
61
+
62
+ The dependency file pins the verified upstream commit. The wheel declares its
63
+ exact package version without embedding a Git URL. Once the plugin is published,
64
+ users with both prerequisites already installed can use
65
+ `python -m pip install flagquantum-compiler-qsteed==0.1.0`.
66
+
67
+ ## Compile a circuit
68
+
69
+ This offline example needs no provider credentials and submits no hardware job:
70
+
71
+ ```python
72
+ import flagquantum as fq
73
+
74
+ circuit = fq.Circuit(3).h(0).cx(0, 2)
75
+ compiled = fq.compile(
76
+ circuit,
77
+ compiler="qsteed",
78
+ target={
79
+ "basis_gates": ("h", "x", "rx", "ry", "rz", "cx"),
80
+ "coupling_map": ((0, 1), (1, 2)),
81
+ },
82
+ )
83
+ print(compiled.instructions)
84
+ ```
85
+
86
+ See [release preparation](RELEASING.md) for publication prerequisites and
87
+ artifact checks.
88
+
89
+ ## Advanced extension lifecycle
90
+
91
+ ```python
92
+ from flagquantum.ecosystem.extensions import (
93
+ CapabilityRequest,
94
+ ExtensionConfig,
95
+ discover_extensions,
96
+ )
97
+
98
+ import flagquantum as fq
99
+
100
+ source_ir = fq.Circuit(3).h(0).cx(0, 2).to_ir()
101
+ registry = discover_extensions("compiler")
102
+ handle = registry.negotiate(
103
+ "compiler",
104
+ "qsteed",
105
+ CapabilityRequest(required=frozenset({"circuit_ir"})),
106
+ )
107
+ handle.start(ExtensionConfig())
108
+ try:
109
+ compiled = handle.invoke(
110
+ "compile",
111
+ source_ir,
112
+ target={
113
+ "basis_gates": ("h", "x", "rx", "ry", "rz", "cx"),
114
+ "coupling_map": ((0, 1), (1, 2)),
115
+ },
116
+ )
117
+ finally:
118
+ handle.close()
119
+ ```
120
+
121
+ QSteed treats the coupling graph as bidirectional in this compiler path. The
122
+ plugin therefore validates two-wire instructions against undirected edges.
@@ -0,0 +1,106 @@
1
+ # FlagQuantum Compiler QSteed
2
+
3
+ `flagquantum-compiler-qsteed` is an independently installed circuit compiler
4
+ plugin for FlagQuantum. It translates FlagQuantum `CircuitIR` to a PyQuafu
5
+ `QuantumCircuit`, invokes QSteed's real transpiler, and translates the compiled
6
+ circuit back to `CircuitIR`.
7
+
8
+ The first release deliberately supports one closed, testable slice:
9
+
10
+ - static `h`, `x`, `rx`, `ry`, `rz`, and `cx` instructions with numeric angles;
11
+ - basis lowering to a selected subset of those gates, with topology routing on
12
+ the fixed six-gate basis;
13
+ - an optional undirected coupling map over the circuit's existing wires;
14
+ - deterministic QSteed basis lowering and SABRE routing;
15
+ - restoration of QSteed's final physical layout to FlagQuantum's logical wire
16
+ order.
17
+ - Quafu calibration targets with automatic or explicitly ordered physical
18
+ subgraph selection and a `target_qubits` result; physical identifiers never
19
+ replace logical QASM wires.
20
+
21
+ Measurements, observables, symbolic parameters, custom matrices, dynamic
22
+ operations, additional target fields, and larger physical topologies are
23
+ rejected. There is no compiler substitution or fallback. Omitting
24
+ `coupling_map` explicitly requests basis compilation without topology routing.
25
+ For a Quafu `chip_info` target, omitting `target_qubits` lets QSteed choose the
26
+ subgraph. Supplying it locks the logical-to-physical order after existence,
27
+ uniqueness, and connectivity validation; the plugin never substitutes another
28
+ mapping.
29
+
30
+ ## Installation
31
+
32
+ This release candidate requires FlagQuantum `>=0.2,<0.3` and the verified
33
+ QSteed build `0.2.3+quafu.sqc`. It is not yet a one-command PyPI installation:
34
+ FlagQuantum 0.2 and this QSteed build must be installed first. PyPI QSteed 0.2.2
35
+ is not a supported substitute. Python 3.12 was used for the release checks;
36
+ the declared Python 3.10–3.12 range still needs a full compatibility matrix.
37
+
38
+ From this repository, after installing a compatible FlagQuantum checkout:
39
+
40
+ ```bash
41
+ python -m pip install -r requirements-qsteed.txt
42
+ python -m pip install -e ".[test]"
43
+ python -m pytest -q
44
+ ```
45
+
46
+ The dependency file pins the verified upstream commit. The wheel declares its
47
+ exact package version without embedding a Git URL. Once the plugin is published,
48
+ users with both prerequisites already installed can use
49
+ `python -m pip install flagquantum-compiler-qsteed==0.1.0`.
50
+
51
+ ## Compile a circuit
52
+
53
+ This offline example needs no provider credentials and submits no hardware job:
54
+
55
+ ```python
56
+ import flagquantum as fq
57
+
58
+ circuit = fq.Circuit(3).h(0).cx(0, 2)
59
+ compiled = fq.compile(
60
+ circuit,
61
+ compiler="qsteed",
62
+ target={
63
+ "basis_gates": ("h", "x", "rx", "ry", "rz", "cx"),
64
+ "coupling_map": ((0, 1), (1, 2)),
65
+ },
66
+ )
67
+ print(compiled.instructions)
68
+ ```
69
+
70
+ See [release preparation](RELEASING.md) for publication prerequisites and
71
+ artifact checks.
72
+
73
+ ## Advanced extension lifecycle
74
+
75
+ ```python
76
+ from flagquantum.ecosystem.extensions import (
77
+ CapabilityRequest,
78
+ ExtensionConfig,
79
+ discover_extensions,
80
+ )
81
+
82
+ import flagquantum as fq
83
+
84
+ source_ir = fq.Circuit(3).h(0).cx(0, 2).to_ir()
85
+ registry = discover_extensions("compiler")
86
+ handle = registry.negotiate(
87
+ "compiler",
88
+ "qsteed",
89
+ CapabilityRequest(required=frozenset({"circuit_ir"})),
90
+ )
91
+ handle.start(ExtensionConfig())
92
+ try:
93
+ compiled = handle.invoke(
94
+ "compile",
95
+ source_ir,
96
+ target={
97
+ "basis_gates": ("h", "x", "rx", "ry", "rz", "cx"),
98
+ "coupling_map": ((0, 1), (1, 2)),
99
+ },
100
+ )
101
+ finally:
102
+ handle.close()
103
+ ```
104
+
105
+ QSteed treats the coupling graph as bidirectional in this compiler path. The
106
+ plugin therefore validates two-wire instructions against undirected edges.
@@ -0,0 +1,42 @@
1
+ # Release preparation
2
+
3
+ Distribution: `flagquantum-compiler-qsteed` 0.1.0.
4
+ Entry point: `flagquantum.extensions` / `compiler.qsteed`.
5
+
6
+ ## Prerequisites
7
+
8
+ - Publish or otherwise provide the compatible FlagQuantum 0.2 release first.
9
+ PyPI FlagQuantum 0.1.1 does not satisfy this plugin's dependency.
10
+ - The verified QSteed build is 0.2.3+quafu.sqc at the commit in
11
+ `requirements-qsteed.txt`. PyPI 0.2.2 failed the offline compilation suite
12
+ with an upstream `NameError` during import in the Python 3.12 check.
13
+ - For now, users must install the pinned QSteed build separately. A complete
14
+ index-only installation requires an upstream indexed release that passes
15
+ these same tests. Do not widen the dependency just to make resolution succeed.
16
+ - Create the intended GitHub repository before advertising its URL. Configure
17
+ the PyPI project and publisher using the maintainer's account; never commit
18
+ API tokens. Repository creation and package publication are separate actions.
19
+ - Complete Python 3.10 and 3.11 compatibility runs before claiming that the
20
+ entire declared range is verified. Python 3.12 is the current tested baseline.
21
+
22
+ ## Validate and build
23
+
24
+ Use a fresh environment with the compatible FlagQuantum release installed:
25
+
26
+ ```bash
27
+ python -m pip install -r requirements-qsteed.txt
28
+ python -m pip install -e '.[test]' build twine
29
+ python -m pytest -q
30
+ python -m build
31
+ python -m twine check --strict dist/*
32
+ ```
33
+
34
+ Install the wheel in another environment with the same dependencies. Run the
35
+ README offline circuit compilation example from outside the source tree and
36
+ confirm discovery through `fq.compile(..., compiler="qsteed")`. Check the
37
+ sdist contains the license, README, dependency file, and tests. Inspect wheel
38
+ metadata for the correct version, dependency constraints, and entry point.
39
+ No test or release check needs to submit a real QPU task.
40
+
41
+ Publish only the exact validated wheel and sdist. Publishing the plugin alone
42
+ does not make its unavailable prerequisite releases appear on PyPI.
@@ -0,0 +1,44 @@
1
+ [build-system]
2
+ requires = ["setuptools>=77", "wheel"]
3
+ build-backend = "setuptools.build_meta"
4
+
5
+ [project]
6
+ name = "flagquantum-compiler-qsteed"
7
+ version = "0.1.0"
8
+ description = "QSteed circuit compiler plugin for FlagQuantum"
9
+ readme = "README.md"
10
+ requires-python = ">=3.10,<3.13"
11
+ license = "Apache-2.0"
12
+ license-files = ["LICENSE"]
13
+ dependencies = [
14
+ "flagquantum>=0.2,<0.3",
15
+ "qsteed==0.2.3+quafu.sqc",
16
+ ]
17
+
18
+ [project.urls]
19
+ Repository = "https://github.com/FlagQuantum/FlagQuantum-Compiler-QSteed"
20
+ Issues = "https://github.com/FlagQuantum/FlagQuantum-Compiler-QSteed/issues"
21
+
22
+ [project.optional-dependencies]
23
+ test = [
24
+ "pytest>=7",
25
+ ]
26
+
27
+ [project.entry-points."flagquantum.extensions"]
28
+ "compiler.qsteed" = "flagquantum_compiler_qsteed:create_extension"
29
+
30
+ [tool.setuptools.packages.find]
31
+ where = ["src"]
32
+
33
+ [tool.black]
34
+ line-length = 88
35
+
36
+ [tool.ruff]
37
+ line-length = 88
38
+
39
+ [tool.ruff.lint]
40
+ select = ["E", "F", "I", "N", "W"]
41
+ ignore = ["E501"]
42
+
43
+ [tool.pytest.ini_options]
44
+ testpaths = ["tests"]
@@ -0,0 +1,2 @@
1
+ # Verified upstream build; install before the plugin.
2
+ qsteed @ git+https://github.com/BAQIS-Quantum/qsteed.git@46584efde731aea9eec27b5466919b76fe5f3184
@@ -0,0 +1,4 @@
1
+ [egg_info]
2
+ tag_build =
3
+ tag_date = 0
4
+
@@ -0,0 +1,5 @@
1
+ """QSteed compiler extension for FlagQuantum."""
2
+
3
+ from .extension import QSteedCompiler, create_extension
4
+
5
+ __all__ = ("QSteedCompiler", "create_extension")