|
62 | 62 |
|
63 | 63 | ### Target Python Versions |
64 | 64 |
|
65 | | -By default, riscv64 wheel should be built for a matrix covering the four latest |
| 65 | +By default, riscv64 wheels should be built for a matrix covering the four latest |
66 | 66 | released Python versions. As of July 14th, 2026, this includes Pythons 3.11, |
67 | 67 | 3.12, 3.13, and 3.14 (along with 3.14t, the freethreaded equivalent). Some |
68 | 68 | wheels have previously been built for 3.13t, but since this was an experimental |
@@ -192,7 +192,7 @@ workflow and retry, while opening an issue to track the musl incompatibility. |
192 | 192 | ### Patching a Project |
193 | 193 |
|
194 | 194 | If a workflow fails consistently when building or testing a module, consider |
195 | | -whether the failure meets one of the following three critieria: |
| 195 | +whether the failure meets one of the following three criteria: |
196 | 196 |
|
197 | 197 | 1. The failure exercises a narrow part of the module's functionality, or relies |
198 | 198 | on external resources (e.g. large downloads over the network) |
@@ -228,8 +228,8 @@ the `main` branch in order to release the wheels to the package registry. |
228 | 228 |
|
229 | 229 | The wheels built by the `python-wheels` project use a variety of open-source |
230 | 230 | licenses. Since RISE is the distributor of riscv64 wheels in the corresponding |
231 | | -package registry, ensuring that the wheels adhere to each project's licensing |
232 | | -requirements. More specifically, check: |
| 231 | +package registry, we must ensure that the wheels adhere to each project's |
| 232 | +licensing requirements. More specifically, check: |
233 | 233 |
|
234 | 234 | 1. The built wheel contains one or more `LICENSE` files corresponding to those |
235 | 235 | contained in the upstream project source. |
|
0 commit comments