deploy: 63e5c52

Author: flpm

.doctrees/environment.pickle

@@ -15,7 +15,7 @@ backend tools.
 
 2. **Python packages with non-Python extensions:** These packages have additional components called extensions written in other languages (such as C or C++). If you have a package with non-Python extensions, then you need to select a build backend tool that allows additional build steps needed to compile your extension code. Further, if you wish to use a frontend tool to support your workflow, you will need to select a tool that supports additional build setups. We suggest that you chose build tool that supports custom build steps like Hatch.
 
-3. **Python packages that have extensions written in different languages (e.g. Fortran and C++) or that have non Python dependencies that are difficult to install (e.g. GDAL)** These packages often have complex build steps (more complex than a package with just a few C extensions for instance). As such, these packages require tools such as [scikit-build](https://scikit-build.readthedocs.io/en/latest/)
+3. **Python packages that have extensions written in different languages (e.g. Fortran and C++) or that have non Python dependencies that are difficult to install (e.g. GDAL):** These packages often have complex build steps (more complex than a package with just a few C extensions for instance). As such, these packages require tools such as [scikit-build](https://scikit-build.readthedocs.io/en/latest/)
    or [meson-python](https://mesonbuild.com/Python-module.html) to build. NOTE: you can use meson-python with PDM.
 
 ## Mixing frontend and backend projects

.doctrees/package-structure-code/complex-python-package-builds.doctree

@@ -526,7 +526,7 @@ <h2>Pure Python Packages vs. packages with extensions in other languages<a class
 <ol class="arabic simple">
 <li><p><strong>Pure-python packages:</strong> these are packages that only rely on Python to function. Building a pure Python package is simpler. As such, you can chose a tool below that has the features that you want and be done with your decision!</p></li>
 <li><p><strong>Python packages with non-Python extensions:</strong> These packages have additional components called extensions written in other languages (such as C or C++). If you have a package with non-Python extensions, then you need to select a build backend tool that allows additional build steps needed to compile your extension code. Further, if you wish to use a frontend tool to support your workflow, you will need to select a tool that supports additional build setups. We suggest that you chose build tool that supports custom build steps like Hatch.</p></li>
-<li><p><strong>Python packages that have extensions written in different languages (e.g. Fortran and C++) or that have non Python dependencies that are difficult to install (e.g. GDAL)</strong> These packages often have complex build steps (more complex than a package with just a few C extensions for instance). As such, these packages require tools such as <a class="reference external" href="https://scikit-build.readthedocs.io/en/latest/">scikit-build</a>
+<li><p><strong>Python packages that have extensions written in different languages (e.g. Fortran and C++) or that have non Python dependencies that are difficult to install (e.g. GDAL):</strong> These packages often have complex build steps (more complex than a package with just a few C extensions for instance). As such, these packages require tools such as <a class="reference external" href="https://scikit-build.readthedocs.io/en/latest/">scikit-build</a>
 or <a class="reference external" href="https://mesonbuild.com/Python-module.html">meson-python</a> to build. NOTE: you can use meson-python with PDM.</p></li>
 </ol>
 </section>