While Faber retains most of the features from Boost.Build, it is
redesigned from the ground up. bjam is still used as scheduling
engine, but everything else is written in Python. In particular,
Jamfiles are replaced by fabscripts, which are essentially Python
scripts. The project contains a range of examples to demonstrate
various simple use-cases, from a simple "hello world" example to
demos involving autoconf-style config checks, and unit testing.
I have added build logic to Boost.Python to use Faber on
Travis-CI as well as AppVeyor, which also is a good litmus test
for Faber's capabilities.
I'd be very interested in feedback as well as contributions.
Perhaps it might become possible one day to integrate Faber with
other efforts to add a Python frontend to Boost.Build.