Skip to content

Commit 9be2c29

Browse files
lwasserNickleDave
andcommitted
Apply suggestions from code review
Co-authored-by: David Nicholson <[email protected]>
1 parent 3c6f7ff commit 9be2c29

File tree

2 files changed

+2
-3
lines changed

2 files changed

+2
-3
lines changed

index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ commonly used in the scientific Python community.
8989

9090
✨ Python packaging tools & structure ✨
9191
^^^
92-
All of the modern tools discussed in this guide will help you build an efficient packaging workflow. This section helps you select the one that will work best for you.
92+
All of the modern tools discussed in this guide will help you build an efficient packaging workflow. This section helps you select the tool that will work best for you.
9393
:::
9494

9595

package-structure-code/complex-python-package-builds.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,7 @@
33
This guide is focused on packages that are either pure-python or that
44
have a few simple extensions in another language such as C or C++.
55

6-
If your package is more complex, [you may want to refer to this guide
7-
created by Ralf Gommers on Python packaging.](https://pypackaging-native.github.io/)
6+
We would love to provide resources on packages with more complex builds. Please feel free to discuss on our board or to open an issue! There are many nuances to building and distributing Python packages that have compiled extensions requiring non-Python dependencies at build time. For an overview and thorough discussion of these nuances, please see [this site.](https://pypackaging-native.github.io/)
87

98
## Pure Python Packages vs. packages with extensions in other languages
109

0 commit comments

Comments
 (0)