Antti Kaihola

I think the stdin mode should only be valid when `rev2` of `-r`/`--revision` is `:WORKTREE:` (the default). Since if the revision to compare is already in Git history, Darker could...

Oh, and @qubidt, isn't there the option to do without an `--stdin-filepath` argument and just make sure the positional `PATH` arguments only point to a single file if a boolean...

Thanks @qubidt for your detailed examples and reasoning. It all makes sense to me. I think we have two good candidates for the command line design: 1) boolean `--stdin` argument...

Black actually has ``` --stdin-filename TEXT The name of the file when passing it through stdin. Useful to make sure Black will respect --force-exclude option on some editors that rely...

Thanks @RishiKumarRay! I guess this is about tholo/pytest-flake8#83 then.

I would rather try to contribute a fix to [pytest-flake8](https://github.com/tholo/pytest-flake8/issues/83). And this is just a deprecation warning so far, so we can afford to wait for some time for the...

But since we do need to fix the same problem in akaihola/pytest-darker#7, we'll probably learn how to fix `pytest-flake8` as well.

Moving this to milestone 1.5.0, there are a plenty of bugfixes and documentation improvements coming up for a 1.4.2 bugfix release already.

In [tholo/pytest-flake8#83](https://github.com/tholo/pytest-flake8/issues/83#issuecomment-1030503256), @jaraco mentions: >See jaraco/pytest-checkdocs#9 and jaraco/pytest-perf#5 for approaches I used to fix this issue. He also writes: >See pytest-dev/pytest#8435 for background I guess I'll take a look at...

With `pytest-flake8==1.1.0` and `pytest==7.0.0` I used to get these: ``` _pytest/nodes.py:146 _pytest/nodes.py:146: PytestDeprecationWarning: is not using a cooperative constructor and only takes {'fspath', 'parent'}. See https://docs.pytest.org/en/stable/deprecations.html#constructors-of-custom-pytest-node-subclasses-should-take-kwargs for more details. warnings.warn(...