python-desert
python-desert
Documentation for - Our workflow - Each stage/job/task Comments in the workflow files would be good.
The ominously numbered [PR #666](https://github.com/python-attrs/attrs/pull/666) has some changes that shouldn't break us but may be worth reviewing. It introduces a new `attrs` namespace, while retaining backward compatibility on the old...
Suppose I have ```py @attr.dataclass class A: color: str @attr.dataclass class C: things: typing.List[A] ``` and I dump some data to disk. Later I change the code to ```py @attr.dataclass...
The requirements files would be better off in a single directory to make them easier to see.
Did we have any changes recently that didn't make it into the change log? Let's document them. Add them to changelog.d/.breaking.rst or .change.rst etc. See the CONTRIBUTING doc.
What needs to happen for a release - bump the version in files - git tag - generate the changelog from .changelog.d - merge into master - publish to PyPI
Maybe every PR should have a changelog entry. The difference between a commit message and a changelog entry is usually said to be that changelog entries are for users and...
There are a few problems. You can see them with `mypy .`. We could also enable some of the stricter mypy flags.