Running pytest (without the dot) seems to work just fine, but running python -m pytest fails.
I think there is a bigger problem here, because miniflasks sys.argv usage seems very intrusive and everything fails when not used directly.
Another example here is the usage of CLI arguments to pytest, e.g. specifically pointing to the test directory via pytest tests/ fails, because miniflask is looking for a module called tests/ 🤔
What's your take on this?

After looking into this again, it seems that this might be related to #114 in my setup.
(Again exactly those tests fail that load the module setup that exists on my setup as a python package. See #114 for details).

I have removed the pytest fix out of this MR and will look into this later again.