Skip to content

docs: Update about custom subpackage name in poetry #8791

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
radoering merged 5 commits into from
Feb 3, 2024
Merged

docs: Update about custom subpackage name in poetry #8791

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
6703456
docs: Update about custom subpackage name in poetry
bigstones Dec 14, 2023
f0d4c90
formatting
radoering Feb 3, 2024
a7b6ef5
line length
radoering Feb 3, 2024
f159a90
remove double newline
radoering Feb 3, 2024
0f64449
readd one newline
radoering Feb 3, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/pyproject.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -214,6 +214,18 @@ packages = [
]
```

The `to` parameter is designed to specify the relative destination path
where the package will be located upon installation. This allows for
greater control over the organization of packages within your project's structure.

```toml
[tool.poetry]
# ...
packages = [
{ include = "my_package", from = "lib", to = "target_package" },
]
```

If you want to restrict a package to a specific build format you can specify
it by using `format`:

Expand Down