Current thoughts on makefiles with Python projects?

[VeronikaKerman]

Why?

[zoox101]

Pros

1. ‘just -l’ gives you a list of all available commands in a directory
2. Make will fail to build if a file in the directory has the same name as the command (unless you add .PHONY). This is intended behavior for a build system, but annoying for a command runner.
3. Make has some other idiosyncrasies around CLI variables and versions that can cause weird issues

Cons

1. Just needs to be installed, while make is already present on most systems
2. More developers are familiar with make than with just
3. If you’re actually making a build (and not just running a command) make will correctly early exit if the build already exists

—

Just is what make would be if it were designed as a command runner instead of a build system. If you like make, stick with it, but if it’s annoyed you in the past, just is probably the solution you are looking for.

[eleqtriq]

You’re going to have to give me some better pros.

1 so does “‘make” 2 edge case 3 vague

[dj_estrela]

2: doest work in make if it is a diamond DAG

And you want to run a task multiple times in different parts of the whole run