Refactor Training Loop into a Class (✓ Sandbox Passed)

[sweep-nightly]

Description

This pull request refactors the training loop in the main.py file into a class called Trainer. It also updates the api.py file to use the Trainer class for loading the model and making predictions.

Summary

• Refactored the training loop in main.py into a Trainer class
• Updated api.py to use the Trainer class for loading the model and making predictions

Fixes #6.

---

🎉 Latest improvements to Sweep:

• Sweep now uses the rope library to refactor Python! Check out Large Language Models are Bad at Refactoring Code. To have Sweep refactor your code, try sweep: Refactor <your_file>.py!
• Sweep finds and fixes bugs in your code by writing unit tests! Check out Having GPT-4 Iterate on Unit Tests like a Human.

---

💡 To get Sweep to edit this pull request, you can:

• Comment below, and Sweep can edit the entire PR
• Comment on a file, Sweep will only modify the commented file
• Edit the original issue to get Sweep to recreate the PR from scratch

[sweep-nightly]

Sandbox Executions

• Ran sandbox for src/main.py. ✓

Sandbox logs for https://github.com/sweepai/evals/commit/7a0e73c7322bb5e768e759e4b59b3cdf8347b506

trunk fmt src/main.py || exit 0 1/2 ✓

 ✔ Formatted src/main.py
Re-checking autofixed files...


Checked 1 file
✔ No issues
Run trunk upgrade to upgrade 1 linter

trunk check --fix --filter=-ruff --print-failures src/main.py 2/2 ✓

Checked 1 file
✔ No issues

• Ran sandbox for src/main.py. ✗

Run `src/main.py` through the sandbox.

• Ran sandbox for src/api.py. ✓

Sandbox logs for https://github.com/sweepai/evals/commit/7cf31a863bab21eb403f4d15ce467e4cd8ecf888

trunk fmt src/api.py || exit 0 1/2 ✓

 ✔ Formatted src/api.py
Re-checking autofixed files...

 ✔ Formatted src/api.py
Re-checking autofixed files...


Checked 1 file
✔ No issues
Run trunk upgrade to upgrade 1 linter

trunk check --fix --filter=-ruff --print-failures src/api.py 2/2 ✓

Checked 1 file
✔ No issues

[sweep-nightly]

Apply Sweep Rules to your PR?

• Apply: All docstrings and comments should be up to date.
• Apply: Code should be properly formatted and indented.
• Apply: Variable and function names should be descriptive and follow a consistent naming convention.
• Apply: Imports should be organized and grouped together.
• Apply: There should be no unused imports or variables.
• Apply: Code should be properly commented and include docstrings for functions and classes.