aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/pyproject.toml (follow)
Commit message (Collapse)AuthorAgeLines
* Prepare for release of 1.0.0HEAD1.0.0trunkWolfgang Müller2024-03-08-1/+1
|
* Update package dependenciesWolfgang Müller2024-03-08-2/+2
|
* Prepare for release of 0.2.00.2.0Wolfgang Müller2023-03-30-1/+1
|
* Migrate to psycopg3Wolfgang Müller2023-03-30-1/+2
| | | | | | SQLAlchemy 2.0 brings support for the latest version of the psycopg PostgreSQL database driver. With the migration to 2.0 done, we can switch to this now.
* Migrate to SQLAlchemy 2.0Wolfgang Müller2023-03-30-1/+1
| | | | | | | | This needs very few changes: - Use declarative_base from sqlalchemy.orm instead of ext [1] - Enable the future flag on both engine and session [1] https://docs.sqlalchemy.org/en/20/errors.html#error-b8d9
* pyproject.toml: Ignore E501 (line-too-long) for ruffWolfgang Müller2023-03-30-0/+1
| | | | | | None of the lines this test affects are worth splitting in our opinion, so disable this warning globally. We'll be the judge about when a line is too long or not for now.
* poetry: Add ruffWolfgang Müller2023-03-30-0/+4
| | | | We want to use ruff instead of pylint.
* Migrate to poetryWolfgang Müller2023-03-30-0/+27
We have used this in another project of ours and prefer its interface over pip's and its toml configuration over setup.py. There should be no functional change.
powered by cgit and git | oriole.systems | how to verify signatures