Skip to content

Commit 37e87a7

Browse files
authored
docs(projects/rye): rm hatch build hook from workspace project file
This aligns with guidance in: DavidVujic/python-polylith#198 and DavidVujic/python-polylith-example-rye@ab029e9
1 parent 5007158 commit 37e87a7

File tree

1 file changed

+2
-5
lines changed

1 file changed

+2
-5
lines changed

docs/projects.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -105,15 +105,11 @@ dev-dependencies = ["polylith-cli"]
105105
```
106106

107107
The default build backend for Rye is Hatch.
108-
Add the `hatch-polylith-bricks` build hook plugin to the `pyproject.toml` file.
109108

110109
``` toml
111110
[build-system]
112-
requires = ["hatchling", "hatch-polylith-bricks"]
111+
requires = ["hatchling"]
113112
build-backend = "hatchling.build"
114-
115-
[tool.hatch.build.hooks.polylith-bricks]
116-
# this section is needed to enable the hook in the build process, even if empty.
117113
```
118114

119115
Make Rye (and Hatch) aware of the way Polylith organizes source code:
@@ -124,6 +120,7 @@ dev-mode-dirs = ["components", "bases", "development", "."]
124120

125121

126122
### The project-specific pyproject.toml file(s)
123+
Add the `hatch-polylith-bricks` build hook plugin to the `pyproject.toml` file.
127124
``` toml
128125
[build-system]
129126
requires = ["hatchling", "hatch-polylith-bricks"]

0 commit comments

Comments
 (0)