Skip to content

Commit 883604e

Browse files
committed
add note about build configuration for dependencies, fix style
1 parent 42409db commit 883604e

File tree

1 file changed

+13
-5
lines changed

1 file changed

+13
-5
lines changed

content/blog/2025-02-xx-announcing-poetry-2-1-0.md

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ $ poetry self update
2525

2626
## Highlights
2727

28-
### Support for Alternative Build Backends in Poetry
28+
### Support for alternative build backends in Poetry
2929

3030
Poetry now supports customizable build backends, allowing greater flexibility based on your project's needs. Previously,
3131
Poetry exclusively used its own build backend, `poetry-core`, when creating packages via the `poetry build` command.
@@ -35,7 +35,7 @@ With this change, the `poetry build` command will fully respect the `[build-syst
3535
`pyproject.toml` file. If the specified build backend differs from the version of `poetry-core` bundled with Poetry, the
3636
build will take place in an isolated environment.
3737

38-
#### Defining Custom Build Backends
38+
#### Defining custom build backends
3939

4040
You can define the build backend in your `pyproject.toml`. For example, to use `maturin` as your build system, specify
4141
it like this:
@@ -48,7 +48,7 @@ build-backend = "maturin"
4848

4949
When running `poetry build`, Poetry will create an isolated environment with the specified requirements.
5050

51-
#### Passing Configuration to Build Systems
51+
#### Passing configuration to build systems
5252

5353
If your chosen build system supports custom configuration settings, these can be passed via the new `--config-settings`
5454
parameter. Use the format `--config-settings <key>=<value>`. You can pass multiple settings by using the parameter
@@ -62,14 +62,22 @@ poetry build --config-settings local-version=some-local
6262

6363
This parameter ensures compatibility with advanced use cases and third-party build backends.
6464

65-
#### Default Behavior When No Build System Is Defined
65+
{{% note %}}
66+
You can pass configuration settings when building a dependency from source.
67+
Since such configuration settings are often platform-dependent this is done via a
68+
[config setting](docs/configuration/#installerbuild-config-settingspackage-name).
69+
{{% /note %}}
70+
71+
#### Default behavior when no build system is defined
6672

6773
Per [PEP 517](https://peps.python.org/pep-0517/), a build tool should fall back to `setuptools` if no build system is
6874
defined in the `[build-system]` section of `pyproject.toml`. However, to avoid immediate disruption, Poetry will
6975
currently issue a **warning** in such cases and continue using the built-in `poetry-core` backend by default.
7076

71-
**Note:** This behavior will change in the next minor release of Poetry. When a `[build-system]` section is not defined,
77+
{{% warning %}}
78+
This behavior will change in the next minor release of Poetry. When a `[build-system]` section is not defined,
7279
Poetry will then default to using `setuptools`.
80+
{{% /warning %}}
7381

7482
## Changelog
7583

0 commit comments

Comments
 (0)