The idea of this PR is to make this tool a bit more useful (and visually appealing). I think generally it is good to have some better profiling tools to explore queries.

EDIT: Initially it was only about the query graph visuals, but I decided to expose the profiling functions enabled in the C++ API (similar to what the Go client does with the C API).

To use the tool:

1. Build this branch (seehttps://duckdb.org/docs/stable/dev/building/python)
2. Run the following in DuckDB

PRAGMA enable_profiling='json';PRAGMA profiling_output='./tmp/profile.json';SELECT ...FROM ...;

3. Run the script (I do it with uv):

uv run python -m duckdb.query_graph tmp/complex_profile.json

If you want to use the profiling within the client:

importduckdbcon=duckdb.connect()con.enable_profiling()con.execute("select 42").fetchall()#or some other eager operationprofile_info=con.get_profiling_information()# optionallycon.disable_profiling()

WIP: Now you can exposetranslate_json_to_html from duckdb.query_graph and do everything within the python process natively:

fromduckdb.query_graphimporttranslate_json_to_html#maybe some better naming heretranslate_json_to_html(input_text=profile_info,output_file='tmp/profile.html')

Which should yield something like the following screenshot: