[krita] [Bug 405796] Python scripting broken (PyQt5 not found by CMake)

2019-03-26 Thread Alvin Wong
https://bugs.kde.org/show_bug.cgi?id=405796 Alvin Wong changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|---

[krita] [Bug 405796] Python scripting broken (PyQt5 not found by CMake)

2019-03-26 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=405796 --- Comment #7 from Boudewijn Rempt --- That's a bit of a poser. For Python 3, we don't need that code, since the new API is selected by default in python 3. But we're vaguely compatible with Python 2, where this is needed. -- You are receiving this m

[krita] [Bug 405796] Python scripting broken (PyQt5 not found by CMake)

2019-03-26 Thread Alvin Wong
https://bugs.kde.org/show_bug.cgi?id=405796 --- Comment #6 from Alvin Wong --- (In reply to Boudewijn Rempt from comment #5) > mikro.py isn't used atm, as far as I remember. I'm not sure why I removed > the private sip stuff; I think I was only experimenting with it. Ok. Should I be worried of t

[krita] [Bug 405796] Python scripting broken (PyQt5 not found by CMake)

2019-03-26 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=405796 --- Comment #5 from Boudewijn Rempt --- mikro.py isn't used atm, as far as I remember. I'm not sure why I removed the private sip stuff; I think I was only experimenting with it. -- You are receiving this mail because: You are watching all bug changes

[krita] [Bug 405796] Python scripting broken (PyQt5 not found by CMake)

2019-03-26 Thread Alvin Wong
https://bugs.kde.org/show_bug.cgi?id=405796 --- Comment #4 from Alvin Wong --- So it looks like PyQt5 is now requiring a private copy of the sip module. From the changelog: 2018-06-17 Phil Thompson * lib/configure.py, rb-product: Use a private copy of the sip module. SIP v4.1

[krita] [Bug 405796] Python scripting broken (PyQt5 not found by CMake)

2019-03-24 Thread Rebecca Breu
https://bugs.kde.org/show_bug.cgi?id=405796 --- Comment #3 from Rebecca Breu --- If PyQt5.QtCore.PYQT_VERSION works for that version, there is no reason not to switch to that. In fact, it seems to be the cleaner solution as it looks like that is where PYQT_VERSION etc are defined in the first pla

[krita] [Bug 405796] Python scripting broken (PyQt5 not found by CMake)

2019-03-24 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=405796 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #2 from Boudewij

[krita] [Bug 405796] Python scripting broken (PyQt5 not found by CMake)

2019-03-24 Thread Rebecca Breu
https://bugs.kde.org/show_bug.cgi?id=405796 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #1 from Rebecca Bre