Noop build with Waf (build system written in Python) takes 0.13s on my system. Waf reports that the build actually takes 0.04s, so I guess 0.09s is Python's start-up time (and some other overhead).
"time bazel" returns 0.098s
Running a null build took 0.84s, but Bazel does significantly more work, as it's working on a big monorepo, as both a build tool and a package manager.
In short, it is not a problem. But I've had npm take many many seconds for simple operations. "npm list" takes 2.9 seconds.
Python can be slow, depending on the tool. Waf sounds like it is simple and fast, but there are lots of other examples of slow python frameworks out there.
For me it returns 1.6s on first run, .9s on second (bazel 0.29.1).
$ time (echo 'quit()' | python)
real 0m0.025s
user 0m0.000s
sys 0m0.031s
$ time (echo 'quit()' | python3)
real 0m0.036s
user 0m0.031s
sys 0m0.016s
(both are after it was already cached)That is probably mostly Waf startup time. Python itself starts way faster than that (on the order of 10-20ms on my machine).
time python -c '' # 0.024s
time python -c 'import argparse' # 0.036s
time python -c 'import argparse, json' # 0.040s
time python -c 'import argparse, json, httplib' # 0.065s