Admin message

Attention: i10git will shutdown soon!

This i10git GitLab server was migrated to gitos.rrze.fau.de due to hardware issues with the current host. This affects all production repositories, including waLBerla, lbmpy, pystencils and HyTeG.

Login: Gitos supports DFN-AAI and eduGAIN. If your institution does not support either, please use our GitHub mirrors.

Onboarding: All repositories belonging to groups were migrated. To regain access, first log in to gitos.rrze.fau.de once to activate your account. Then email cs10-admin@fau.de with your old i10git and your new gitos.rrze username (the @) as shown on your respective user profiles. We will reassign your accordingly. Note: Repositories from former courses (e.g. advpt) were not migrated.

Personal repositories in individual user namespaces were not migrated. Please export these yourself before the old server is shut down.

Expected shutdown by the end of 2026. Until then, the old i10git server will still be reachable with all repositories archived (read only). However, due to the ongoing hardware issues, it may remain unreliable and will receive no further maintenance.

The parent group is archived. This project and its data are read-only.
Modernize pystencils' dev environment
We should modernize the development environment of pystencils to latest Python practice. This includes: ### pyproject.toml We should migrate from the `setup.py` paradigm of `setuptools` to the now-standard `pyproject.toml` ([PEP 518](https://peps.python.org/pep-0518/)) for the basic build system configuration. This way, we can enjoy all the helpful tools that now base themselves on `pyproject.toml` (see 'Dependency Management' below). Still, some tool-specific stuff may have to remain in `setup.py`. ### Dependency Management Currently, as far as I am aware, setup of a dev environment for pystencils depends on `requirements.txt` files flying around wildly. To consolidate and clearly define a uniform development environment. we should instead introduce a packaging and dependency manager into the project - I'd recommend [pdm](https://pdm-project.org/latest/). This way, all developers would get the exactly same environment, with exactly the same versions of all required dependencies - including dev and build dependencies like `flake8`, `sphinx`, etc. ### Type Checking pystencils has become a vast package with many moving parts, and as a generator of exectuable code, a high level of correctness is expected of it. While extensive unit tests are a necessary tool to achieve correctness, they can never be entirely watertight. Being written in Python, users and developers of pystencils enjoy great flexibility due to Python's dynamic type system. However, that same type system may also permit a much larger number of (potential) bugs to go unnoticed for a very long time. To alleviate this issue, Python itself has been gradually introducing and improving its system of type hints, which although are not mandatory nor do they affect the code in any way by themselves. However, type checkers like [mypy](https://www.mypy-lang.org/) have been developed on top of that to statically check the types in Python code. In particular in the context of pycodegen/pystencils#73, we should gradually introduce thorough static type checking into pystencils. This will help to make the code more robust and achieve a higher level of correctness a-priori. Types can be checked on developer's machines (e.g. as a hook to `git add`/`git commit`) and in the CI (much like linting with `flake8`).
issue