GitAuto: Update pyqt5 to the latest version pyqt6

[gitauto-for-dev[bot]]

Resolves #1

What is the feature

Upgrade the application from using PyQt5 to PyQt6.

Why we need the feature

Upgrading to PyQt6 ensures that the application benefits from the latest features, performance improvements, and security patches provided by the newer version of the library. It also helps maintain compatibility with the latest versions of Python and Qt, ensuring long-term support and stability for the application. Additionally, moving to PyQt6 prepares the codebase for future developments and reduces technical debt associated with outdated dependencies.

How to implement and why

1. Update Dependency Files:

   • Modify requirements.txt and requirements.pytorch.txt to replace PyQt5 with PyQt6.

     - PyQt5>=5.15.0
     + PyQt6>=6.0.0

   • This ensures that the correct version of PyQt is installed when setting up the environment.

2. Update Import Statements:

   • In the game_manager directory and any other modules that import PyQt5, update import statements.

     - from PyQt5 import QtWidgets, QtCore, QtGui
     + from PyQt6 import QtWidgets, QtCore, QtGui

   • This is necessary because the package namespace has changed in PyQt6.

3. Address API Changes:

   • PyQt6 has made several changes to enums and other APIs. Adjust code to accommodate these changes.
     • Enums are now accessed via the module rather than directly.

     • alignment = QtCore.Qt.AlignCenter
     • alignment = QtCore.Qt.AlignmentFlag.AlignCenter

     • Methods that previously returned tuples now return objects.
   • Update any deprecated methods or classes to their PyQt6 equivalents.

4. Adjust QtCore QtGui Mappings:

   • Some classes have moved between modules.
     • For example, QtGui.QFont might now be accessed from QtGui or QtWidgets depending on the class.
   • Ensure all class references are correctly updated.

5. Test the Application:

   • Thoroughly test all functionalities, especially GUI components, to identify any runtime issues.
   • Pay particular attention to custom widgets and signal-slot connections.

6. Update Documentation:

   • Review and update documentation in the doc directory to reflect the changes.
   • Update the README.md if there are any new setup instructions or considerations.

7. Docker and Deployment Configurations:

   • If the application is deployed using Docker (as indicated by docker-compose.yaml), ensure the Docker images and containers are updated to include PyQt6.
   • Update any Dockerfiles in the docker directory accordingly.

About backward compatibility

Upgrading to PyQt6 may introduce compatibility issues with environments that only support PyQt5 or older versions of Qt. PyQt6 requires Python 3.6 or higher and leverages newer Qt libraries. If backward compatibility is a concern for users on legacy systems, consider:

• Maintaining a separate branch that continues support for PyQt5.
• Providing clear documentation on how to use the PyQt5 version.
• Noting the upgrade in release notes and communicating the changes to all stakeholders.

However, prioritizing the upgrade will align the application with current standards and is beneficial for future development.

Test these changes locally

git checkout -b gitauto-wes/issue-1-a480b13f-be55-4aca-b25c-4fbed74eaba5
git pull origin gitauto-wes/issue-1-a480b13f-be55-4aca-b25c-4fbed74eaba5

[gitauto-for-dev[bot]]

▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 30% Planning how to fix the error...

[gitauto-for-dev[bot]]

Committed the Check Run build (3.10) error fix! Running it again...

[gitauto-for-dev[bot]]

Committed the Check Run MSBuild (3.9) error fix! Running it again...

[gitauto-for-dev[bot]]

Committed the Check Run MSBuild (3.10) error fix! Running it again...