[mutmut3] --paths-to-mutate support?

[przybylop]

mutmut 2.x. had --paths-to-mutate argument support:

mutmut/mutmut/__main__.py

Lines 317 to 318 in bdd8c37

	if paths_to_mutate is None:
	paths_to_mutate = guess_paths_to_mutate()

whereas it was removed in mutmut 3.x:

mutmut/mutmut/__main__.py

Lines 150 to 151 in e8e0960

	def walk_all_files():
	paths = [guess_paths_to_mutate()]

but README still mentions it:

mutmut/README.rst

Lines 55 to 59 in e8e0960

	.. code-block:: ini
	[mutmut]
	paths_to_mutate=src/
	tests_dir=tests/

and the error message in guess_paths_to_mutate() as well:

mutmut/mutmut/__main__.py

Lines 128 to 131 in e8e0960

	raise FileNotFoundError(
	'Could not figure out where the code to mutate is. '
	'Please specify it on the command line using --paths-to-mutate, '
	'or by adding "paths_to_mutate=code_dir" in setup.cfg to the [mutmut] section.')

is the argument going to be reintroduced?

[boxed]

No. Arguments for conf was a mistake I think. All the conf should always go into the conf file.

Thanks for the heads up on the docs issue. I will fix that.

[przybylop]

Thanks for the quick response!

What about the paths_to_mutate argument from config file? mutmut 3.x ignores it as well

[boxed]

Oh. Well that is a mistake then. It should make good guesses, but when it fails it should read that.

[awgymer]

It should make good guesses, but when it fails it should read that.

Would it not make more sense for it to short-circuit to the conf value if it's set, rather than fall back to it. If it's only used as a fallback it means you can't ever run mutmut in a repo which had e.g. a src folder which did not contain the paths to mutate

[boxed]

Sorry, yea I was sloppy with my language. The conf should override for sure.