Introduce Pipenv

Replace requirements.txt with pipenv for consistent development environments. Pipenv maintains a superior Lockfile similar to NPM. Added additional development dependencies and mypy configuration.

This contains a package update too:

• alembic from 1.12.1 to 1.13.2
• flask from 3.0.0 to 3.0.3
• SQLAlchemy from 2.0.23 to 2.0.31

requested review from @moser

assigned to @karp

marked this merge request as draft

@karp Thank you for the time and effort to prepare this MR. I have three questions:

• Could you explain to me how pipenv is used, please? I haven't used it yet, and would like a few pointers. Maybe even add something to the README, so others can profit from it too :)
• Could you adjust the Dockerfile so that it uses pipenv? Currently, I think merging this MR would break the pipeline.
• Is it intentional that the dependencies in the Pipfile currently have * instead of version numbers? Does that have something to do with the locking mechanism?

added 2 commits

• b6a559b9 - Update Dockerfile
• 770c2d2b - Update README.md

Compare with previous version

@moser Pipenv captures the version numbers within the Pipfile.lock which is used to track the last working combination of package versions. Once you have installed pipenv in your global python version via pip install pipenv you can create an environment via pipenv --python 3.12, switch into the environment via pipenv shell and install dependencies with pipenv install --dev (without --dev development deps are excluded).

changed the description

added 1 commit

• ce0cf990 - Remove pipenv env statement

Compare with previous version

marked this merge request as ready

approved this merge request

mentioned in commit 3807efc6

merged

@karp Thanks for the explanation, approved and merged!