From 0ad179719c66e70611744dd7d2ee37568674cca5 Mon Sep 17 00:00:00 2001 From: Saransh Chopra Date: Mon, 12 Aug 2024 16:38:28 +0100 Subject: [PATCH] More src migration + format MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: David Pérez-Suárez --- ch04packaging/03Packaging.ipynb.py | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/ch04packaging/03Packaging.ipynb.py b/ch04packaging/03Packaging.ipynb.py index 334df2f7..6b2cd60e 100644 --- a/ch04packaging/03Packaging.ipynb.py +++ b/ch04packaging/03Packaging.ipynb.py @@ -129,7 +129,7 @@ # In this case, we'll be using `hatch` to build our package, so we list it in the `requires` field. Technically speaking, `hatch` is the front-end (a CLI utility) # for the actual build-backend `hatchling`. `hatchling` is installed with hatch and can be specified as the `build-backend` in `pyproject.toml`. # -# Finally, we can set specific options for `hatch` using additional sections in `pyproject.toml`: in this case, we will tell `hatch` that it needs to find **and include** all of the files in our `greetings` folder. +# Finally, we can set specific options for `hatch` using additional sections in `pyproject.toml`: in this case, we will tell `hatch` that it needs to find **and include** all of the files in our `src` folder. # The best way to look at all the options of a build-backend is by going through its documentation. # %% @@ -151,6 +151,7 @@ # %% [markdown] # Some of the build-backends allow users to automate the package's version using VCS. # For instance, you might want to look into [`hatch-vcs`](https://github.com/ofek/hatch-vcs) to enable VCS versioning with `hatch`. +# # We can now install this "package" with pip (make sure `hatch` is installed): # %% language="bash" @@ -410,7 +411,7 @@ def process(): [tool.hatch.build.targets.sdist] include = [ - "greetings/", + "src/", ]