Skip to content

Commit 6a75b6b

Browse files
henryiiibhrutledge
andcommitted
Apply suggestions from code review
Co-authored-by: Brian Rutledge <brian@bhrutledge.com>
1 parent 4babf0d commit 6a75b6b

1 file changed

Lines changed: 4 additions & 5 deletions

File tree

source/guides/packaging-binary-extensions.rst

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -232,16 +232,15 @@ guide includes an introduction to writing a
232232
Building binary extensions
233233
==========================
234234

235-
Building extensions in CI
235+
Building extensions for multiple platforms
236236
-------------------------
237237

238-
If you plan to distribute your modules, you should provide builds for all the
238+
If you plan to distribute your extension, you should provide :term:`wheels <Wheel>` for all the
239239
platforms you intend to support. For most extensions, this is at least one
240-
module per Python version times the number of OS and archetectures you support.
240+
package per Python version times the number of OS and architectures you support.
241241
These are usually built on continous integration (CI) systems. There are tools
242242
to help you build highly redistributable binaries from CI; these include
243-
`cibuildwheel <https://cibuildwheel.readthedocs.io>`__ and
244-
`multibuild <https://github.com/matthew-brett/multibuild>`__.
243+
:ref:`cibuildwheel` and :ref:`multibuild`.
245244

246245

247246
Binary extensions for Windows

0 commit comments

Comments
 (0)