fix(graders): fix typo in code_execution filename and imports

[XiaoBoAI]

• Rename code_excution.py to code_execution.py (fix typo)
• Fix imports in code/init.py: open_judge -> openjudge
• Remove commented-out import in base_grader.py

OpenJudge Version

[The version of OpenJudge you are working on, e.g. import openjudge; print(openjudge.__version__)]

Description

[Please describe the background, purpose, changes made, and how to test this PR]

Checklist

Please check the following items before code is ready to be reviewed.

• Code has been formatted with pre-commit run --all-files command
• All tests are passing
• Docstrings are in Google style
• Related documentation has been updated (e.g. links, examples, etc.)
• Code is ready for review

[gemini-code-assist]

Summary of Changes

Hello @XiaoBoAI, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on code hygiene and correctness by addressing several minor issues. It primarily fixes a typo in a filename and updates corresponding import paths, alongside removing a redundant commented-out line of code. These changes improve code consistency and maintainability without altering functionality.

Highlights

• Typo Fix: Filename: The file code_excution.py has been renamed to code_execution.py to correct a spelling error.
• Import Path Correction: Imports within openjudge/graders/code/__init__.py have been updated to reflect the corrected filename and to use openjudge instead of open_judge as the package name.
• Code Cleanup: A commented-out import statement (# import inspect) has been removed from base_grader.py.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request provides several useful cleanups, including fixing a typo in a filename, standardizing the package name in imports, and removing commented-out code. The changes are correct and improve code quality. I have one suggestion regarding the use of relative imports in openjudge/graders/code/__init__.py to improve conciseness, which you can find in the detailed comments. Overall, this is a good set of fixes.