Pull Request Description

Title: Remove Redundant python3 Calls and Use python Instead

Related Issue: # Issue Title: Redundant python3 call

Background:
In our current setup, the code is invoking python3 for executing scripts even after successfully activating the virtual environment. This reliance on the system's python3 can lead to inconsistencies, particularly if different environments or versions of Python are being used across different systems. By making our project self-contained and fully utilizing the python command from the activated environment, we can ensure that the intended version of Python is consistently used, thereby reducing potential errors or conflicts.

Summary of Changes:
This pull request implements the following changes to resolve the redundant use of python3:

1. Refactored Code Base:

   • All instances of python3 have been replaced with python in the relevant scripts and command-line instructions.
   • Verified that the use of python operates correctly in a properly activated virtual environment.

2. Documentation Updates:

   • Updated the README and any associated documentation to reflect the change from python3 to python.
   • Added a section explaining the importance of ensuring the virtual environment is activated when running the project.

3. Testing:

   • Conducted tests in different environments to confirm that replacing python3 with python functions correctly without any introduction of issues.
   • Ensured backward compatibility and proper functionality across systems.

Resolution Benefits:

• Self-Containment: This change enhances the portability of the project by ensuring that it works off the environment it is set within, rather than depending on the system-level Python installation.
• Error Reduction: Reducing reliance on external Python versions decreases the likelihood of encountering version-related bugs.
• Clarity and Consistency: With a unified command for invoking Python, new developers or users of the project will find it easier to understand and use the codebase.

Next Steps:

• Review the changes in this pull request.
• Test the updated code in your environment to verify consistent functionality.
• Once approved, we will merge this change into the main branch.

Thank you for considering this important improvement for our project's maintainability and user experience!