Metaculus / Metaculus/forecasting-tools
Refactor codebase to avoid circular import issues
Open
@alex-costea is already working on this.
Since Dec 2, 2025.
- Dominant language
- Python
- Stars
- 79
- Forks
- 38
- Avg merge
- 20m
- Merged PRs (30d)
- 12
Description
In particular, in my opinion some pain points are:
- Predictions and Reports in the same file
- All question types in the same file
- Reports having
publish_report_to_metaculus- should be refactored into its own service
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.