Skip to content

Commit

Permalink
Update package-structure-code/complex-python-package-builds.md
Browse files Browse the repository at this point in the history
Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
  • Loading branch information
ucodery and willingc authored Apr 9, 2024
1 parent 189be09 commit 215ba59
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion package-structure-code/complex-python-package-builds.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ some back-ends (`poetry`) only work with a single back-end (`poetry-core`). Refe
more information about front-end and back-end compatibility.

In this packaging guide we recommend using `hatch` along with it's preferred back-end `hatchling`. One reason to use
hatch with an alternate back-end is for creating an extension module. A Python extension module is one that is make up,
hatch with an alternate back-end is for creating an extension module. A Python extension module is one that is made up,
either in part or entirely, of compiled code. In this case the back-end chosen (such as `meson-python`) must know how to
compile the extension language and bind it to Python since `hatchling` is only capable of building pure Python modules.

Expand Down

0 comments on commit 215ba59

Please sign in to comment.