@Ronis_BR I did hit another blocker today. CUDA.jl also needs an update after DataFrames.jl.
I am actually surprised that CUDA.jl depends on DataFrames.jl and PrettyTables.jl. There is definitely room for improvement there.
Opened an issue:
opened 01:41PM - 27 Aug 25 UTC
enhancement
It is a heavy dependency, and I wonder if it could be replaced by built-in table… types (e.g., named tuples of vectors) provided by the language.
1 Like
The direct calls to PrettyTables.jl in CUDA.jl are here:
formatters = function(v, i, j)
if v === missing
return "-"
elseif names(df)[j] in ["start", "time"]
format_time(v)
else
v
end
end
highlighters = time_highlighters(df)
pretty_table(io, df; header, alignment, formatters, highlighters, crop,
body_hlines=trace_divisions)
else
df = summarize_trace(df)
columns = [:time_ratio, :time, :calls]
if any(!ismissing, df.time_dist)
push!(columns, :time_dist)
end
push!(columns, :name)
df = df[:, columns]
It should be really simple to update! However, I cannot test since I have no nvidia gpu
I believe their CI infrastructure covers it. We can submit a PR and wait for action.
1 Like
Awesome! Can you do this please while I am working in DataFrames.jl?
1 Like
tchr
August 27, 2025, 1:49pm
46
I don’t need any .pdf documents (I don’t quite understand the LLM suggestion from @karei here); just an indication of what has changed. The “everything might have changed” is quite daunting honestly. Or, if that’s easier: what has stayed the same?
@Ronis_BR we can only run CUDA.jl tests after DataFrames.jl is released with support to PrettyTables.jl v3. I can try to prepare the PR to CUDA.jl after your DataFrames.jl PR is ready
1 Like
You probably can have all those answers here:
@juliohm The PR to migrate DataFrames.jl is already submitted:
main
← ronisbr:pretty_tables_v3
opened 04:41PM - 27 Aug 25 UTC
The PR updates the support in DataFrames.jl to PrettyTables.jl v3. I’ve also upd… ated the API call and the tests. As we can see from the tests, the output changes are minor. For the user, the printed version of DataFrames.jl should look exactly the same except in very edge cases.
@bkamins I reviewed the list of open display-related issues, and I can address some of them. However, this migration is currently blocking some internal workflows because we can’t use DataFrames with PrettyTables v3 simultaneously. Could we please merge this support, and then I’ll handle the remaining issues?
1 Like