Daniel Weindl

The problem is the `all` here https://github.com/snakemake/snakemake/blob/c8d81d03de2885d5d0473084141e9f6abc5de445/snakemake/executors/__init__.py#L469 in combination with the early return in https://github.com/snakemake/snakemake/blob/c8d81d03de2885d5d0473084141e9f6abc5de445/snakemake/logging.py#L433-L435 This was introduced in https://github.com/snakemake/snakemake/commit/c8d81d03de2885d5d0473084141e9f6abc5de445#diff-438f3317205fd7130727d0589d2fc1a6c2e1f6fc48c2c04d354a8a09b91ba2f4 Last unaffected version is `v7.6.2`.

Not sure I get what you mean. I'd just not import all samplers here, as in most cases, users will use only one of those.

I vote for [YAML](https://en.wikipedia.org/wiki/YAML) and could also live with less readable JSON. I think specifying lists and dictionaries in .ini is no fun.

This is only loosely related to PEtab. Renaming.

@yannikschaelte Any progress or concrete plans here?

> https://bitbucket.org/DavidPenas/sacess-library/src/master/ looks like good old C to me, not matlab. Includes good old Fortran as well :D

> https://bitbucket.org/DavidPenas/sacess-library/src/master/ looks like good old C to me, not matlab. Oh, and if somebody decides to look into sacess code, I am happy to discuss. Would be interesting to...

Still happening... https://github.com/ICB-DCM/pyPESTO/actions/runs/3280972663/jobs/5402409945

> What's your opinion on that @FFroehlich, @yannikschaelte, @dweindl ? Pretty much what was said already. Should definitely make use of AMICI `amici_solver.setReturnDataReportingMode` (I thought I was told this was...

- [x] PyMC3 tests and examples have been temporarily disabled in https://github.com/ICB-DCM/pyPESTO/pull/831. They should be re-enabled here with their PyMC4 counterparts