Do you have questions or issues? Join our chat!
If you want to start working on this project, you will need to get familiar with these concepts:
- http://learnyouahaskell.com/functors-applicative-functors-and-monoids
- https://github.com/dbrattli/OSlash/wiki/Functors,-Applicatives,-And-Monads-In-Pictures
- https://gcanti.github.io/fp-ts/ and https://dev.to/gcanti
Here are some practical examples of what we are doing here:
- https://medium.com/@rnesytov/using-Result-monad-in-python-b6eac698dff5
- https://www.morozov.is/2018/09/08/monad-laws-in-ruby.html
- https://beepb00p.xyz/mypy-error-handling.html
We use poetry to manage the dependencies.
To install them you would need to run the install command:
poetry installTo install extra dependencies for working on the hypothesis or mypy plugin:
poetry install --extras check-laws
poetry install --extras compatible-mypyTo activate your virtualenv run eval $(poetry env activate).
To make local development easier, all common commands are available
via the Makefile. Run make help to see all available targets:
make helpMain targets:
make format— format and autofix code withruffmake lint— run all linting checks (ruffandflake8)make type-check— runmypytype checksmake unit— run standard tests withpytestmake typesafety— run type-safety tests (pytest-mypy-plugins)make slots— check__slots__correctness withslotscheckmake package— check package dependencies withpip checkmake test— run all checks: lint, type-check, unit tests, slots, and package
We use pytest and flake8 for quality control.
We also use wemake_python_styleguide and ruff to enforce code quality.
To run standard tests:
poetry run pytest returns docs/pages testsOr simply:
make unitNOTE: type-safety tests not included, see section on type tests below
To run linting:
poetry run flake8 .
poetry run ruff check --exit-non-zero-on-fix
poetry run ruff format --check --diffOr simply:
make lintKeep in mind: default virtual environment folder excluded by flake8 style checking is .venv.
If you want to customize this parameter, you should do this in setup.cfg.
These steps are mandatory during CI.
We use pre-commit to run some checks
automatically before each commit. Among others, it runs ruff check
and ruff format on the changed files.
To install the hooks, run:
poetry run pre-commit installTo run all hooks manually:
poetry run pre-commit run --all-filesWe also use pytest-mypy-plugins. Tests cases are located inside ./typesafety
If you create new types or typed functions, it is required to test their types.
The type-safety tests can be run with the following:
poetry run pytest typesafetyOr simply:
make typesafetyNOTE: This can take upwards of 20 minutes, only recommended to run if necessary.
Here's a helpful tutorial if you are looking for more information.
We use mypy to run type checks on our code.
To use it:
poetry run mypy returns
poetry run mypy docs testsOr simply:
make type-checkThis step is mandatory during CI.
We use trunk based
development (we also sometimes call it wemake-git-flow).
What the point of this method?
- We use protected
masterbranch, so the only way to push your code is via pull request - We use issue branches: to implement a new feature or to fix a bug
create a new branch named
issue-$TASKNUMBER - Then create a pull request to
masterbranch - We use
git tags to make releases, so we can track what has changed since the latest release
So, this way we achieve an easy and scalable development process which frees us from merging hell and long-living branches.
In this method, the latest version of the app is always in the master branch.
Before submitting your code please do the following steps:
- Run
make unit(orpytest) to make sure everything was working before - Add any changes you want
- Add tests for the new changes
- Edit documentation if you have changed something significant
- Update
CHANGELOG.mdwith a quick summary of your changes - Run
make formatto format the code withruff - Run
make testto run all checks: linting (ruff,flake8),mypytypes,pytesttests,slotscheck, andpip check
You can contribute by spreading a word about this library. It would also be a huge contribution to write a short article on how you are using this project. You can also share your best practices with us.