rechu 0.0.2

Receipt cataloging hub for detailed personal finance tracking

Receipt cataloging hub

This repository contains a Python module that implements a database system for reading digitized receipts for detailed product purchases. The receipts, shops and product metadata can be written first in YAML files and imported or they may be created through interactive commands.

The module is written for Python 3.10+ and supported database backends are SQLite and PostgreSQL. It is currently in alpha phase and is meant to be developed with more features for reporting, external data and so on. Detailed information on changes for each version is found in the changelog file. Most recent information on installation, configuration, usage and programming interfaces is found in the documentation.

Installation

To obtain the latest release version of the module and its dependencies from PyPI, use uv add rechu, pip install rechu or poetry add rechu.

Source releases of versions are available from GitHub.

When using the source release or if this repository is cloned, then installation of the module is possible with uv add or pip install followed by one of the following: a wheel, a release zip/tarball or a path to the current directory. make install installs from the current directory. We recommend using virtual environments to keep your dependencies separate from global installation.

To install a development version of the module as a dependency, you can use rechu @ git+https://github.com/lhelwerd/rechu.git@main#egg=rechu in a pyproject.toml project dependencies or similar file.

Running

After installation, the rechu command should be available in your environment to run various subcommands, but it has not been configured and set up with any data sources and database connection.

In order to run the module, first place a settings.toml file in the directory from which you will use the module, which might be the current directory. Either use rechu config > settings.toml or (when using the source release or if this repository is cloned) copy the example rechu/settings.toml file with default values to another settings.toml file, then edit the new file to adjust values in it. If you plan to use this package as a dependency in your own module, then you can also override the values in a pyproject.toml file using [tool.rechu...] sections.

To create the database schema in the database path defined in the settings, use rechu create. Then, you can create receipts and products with rechu new; this command writes the new receipts and product metadata to YAML files in the defined path/filename format and imports them to the database, keeping both in sync. You can also bulk-import YAML files for receipts, shop and product inventories from the defined path, receipt subdirectory pattern, shop path and product pattern with rechu read; you can later use the same command to synchronize changes in YAML files to the database.

When you install a new version of this package, there may be database schema changes which need to be applied to continue using the current model. After backing up your database, you should run rechu alembic upgrade head to migrate your database to the proper version. This command will use the database connection configured in your settings.toml file.

Some additional scripts that do not use the database are available in the scripts directory in the repository. These are mostly meant for experiments, simple reporting and validation.

Development and testing

The module is tested with unit tests that are run on pytest. In the repository, first install dependencies with make setup_test, then run unit tests using make test. Additionally, obtain coverage information by using make coverage to perform the unit tests and receive output in the form of a textual report and XML report. Finally, an HTML report is obtainable with coverage html.

Typing and style checks are also possible by first installing dependencies using make setup_analysis. Then, use make mypy to run the type checker and receive HTML and XML reports. Style checks are done by using make pylint for an aggregate report output.

The unit test coverage, typing coverage, style checks and schema validation is combined in one GitHub Actions workflow which is run on commits to the main branch and pull request changes. Unit test coverage is then stored for comparative purposes via the interface at Coveralls. The tests and coverage results are combined with analysis results (including typing checks and coverage by basedpyright and mypy, code formatting style checks from ruff and pylint and JSON schema validation) as part of a quality gate on SonarCloud.

License

The receipt cataloging hub module is licensed under the MIT License. See the license file for more information.