Update Python to 3.13

Freya Lupenrequested to merge
freyalupen/krita:freyalupen/transition.now/python-313 into master

Temporarily switches Krita to use the Python 3.13 deps branches, to make sure it works on all platforms.

Also, autodetect the version number of Python in build-image.sh, instead of hardcoding it in the path names.

See Issue #5 (closed)

Test Plan

Compile and run Krita on all platforms other than Android, make sure Python scripting still works. (Run this script in Scripter:)

from krita import *
import platform
print(f"Scripting in Python {platform.python_version()} " +
      f"on Krita {Krita().version()} " +
      f"with Qt {QT_VERSION_STR} " +
      f"and PyQt {PYQT_VERSION_STR}")
  • Linux Qt5
  • Linux Qt6
  • Windows Qt5
  • Windows Qt6
  • macOS Qt5
  • macOS Qt6

Also, make sure none of Krita's builtin plugins are broken by the Python update (probably not).

Formalities Checklist

  • I confirmed this builds.
  • I confirmed Krita ran and the relevant functions work.
  • I tested the relevant unit tests and can confirm they are not broken. (If not possible, don't hesitate to ask for help!)
  • I made sure my commits build individually and have good descriptions as per KDE guidelines.
  • I made sure my code conforms to the standards set in the HACKING file.
  • I can confirm the code is licensed and attributed appropriately, and that unattributed code is mine, as per KDE Licensing Policy.
  • Does the patch add a user-visible feature? If yes, is there a documentation MR ready for it at Krita Documentation Repository?

Reminder: the reviewer is responsible for merging the patch, this is to ensure at the least two people can build the patch. In case a patch breaks the build, both the author and the reviewer should be contacted to fix the build. If this is not possible, the commits shall be reverted, and a notification with the reasoning and any relevant logs shall be sent to the mailing list, kimageshop@kde.org.

Edited by Freya Lupen

Merge request reports