Skip to content
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.

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

Use pyproject.toml by default and fix config merger #35

Merged
merged 3 commits into from
Nov 8, 2024
Merged

Conversation

simonrainerson
Copy link
Member

Switch to pyproject.toml and also fix config merger. See commits for more info.

Fixes #34

Make Added/Fixed etc sub headers of the release.
Apart from the already supported override:
```
[[tool.mypy.overrides]]
module = "some.module.name"
```

mypy also supports overringing multiple modules at once:
```
[[tool.mypy.overrides]]
module = ["some.module.name", "some.other.module.name"]
```

Made the non-list case into a list to have a uniform handling of it.
Also made it merge the different overrides of the same module.
The days of setuptools are numbered! Switch default component to use
pyproject.toml, it is currently the least deprecated way of building
python packages.

Also sneak in some nifty features like adding a `run` command for
clients and services. And add a corresponding entry point to their
package.

Also made the generated code pass `ruff`, it uses the
`--unsafe-fixes` to add period at the end of docstrings if missing.
Since it only runs on the templated code we know that it won't do
anything else.
@abbec abbec merged commit aa5b559 into main Nov 8, 2024
7 checks passed
@abbec abbec deleted the python-upgrades branch November 8, 2024 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Python's config merger doesn't handle multi module override
2 participants