On a fresh checkout make init runs scripts/init.py twice.
The most likely cause: the Makefile has -include .env at the top and a .env: rule that runs init.py (Makefile:262-263). GNU make remakes an included file before it runs any target, so .env gets built first, and then the init recipe (Makefile:269-271) runs init.py again.
Harmless while init.py stays idempotent, and a trap the day it does not. It also prints everything twice.
- Make
init depend on .env and drop its own init.py call, or the other way round. One path, not two.
Done when a fresh make init runs init.py once.
On a fresh checkout
make initrunsscripts/init.pytwice.The most likely cause: the Makefile has
-include .envat the top and a.env:rule that runsinit.py(Makefile:262-263). GNU make remakes an included file before it runs any target, so.envgets built first, and then theinitrecipe (Makefile:269-271) runsinit.pyagain.Harmless while init.py stays idempotent, and a trap the day it does not. It also prints everything twice.
initdepend on.envand drop its own init.py call, or the other way round. One path, not two.Done when a fresh
make initruns init.py once.