MultiBacktest - why no stats returned?
- Dominant language
- Python
- Stars
- 9k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
### Discussed in https://github.com/kernc/backtesting.py/discussions/1307
Originally posted by **acud** September 11, 2025
I just tried the `MultiBacktest` and saw that it only returns the heatmaps, but not the stats. I wonder, since it wraps the optimize function, why not return the stats for every symbol too? It is a bit difficult to see what are the optimization results without seeing all the relevant data coming out of the stats too. Any particular reason why those weren't included?
> the function fingerprint could be more like `Backtest`, with `best_stats` and then `heatmaps` conditionally returned. 👍
Contributor guide
Research direction
Start by reading the MultiBacktest implementation and its wrapping of optimize, then compare its return handling with Backtest. Determine how stats for each symbol should accompany the existing heatmaps, and verify the public result exposes the relevant optimization data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100