https://bugs.kde.org/show_bug.cgi?id=415048
Rik Mills changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=415048
--- Comment #4 from Rik Mills ---
No, it was this commit in the scripting dir that must have made me think it was
or should supported.
https://cgit.kde.org/kig.git/commit/scripting?h=release/19.12&id=c0aa768f28219ce8b3c275a6d13ad69757e3c7af
"Try to fi
https://bugs.kde.org/show_bug.cgi?id=415048
--- Comment #3 from David E. Narvaez ---
(In reply to Christoph Feck from comment #2)
> Not sure if there is more Python usage in Kig,
There is.
> but pykig was recently ported
> to Python3, see https://phabricator.kde.org/D25982
Right, and I believe
https://bugs.kde.org/show_bug.cgi?id=415048
--- Comment #2 from Christoph Feck ---
Not sure if there is more Python usage in Kig, but pykig was recently ported to
Python3, see https://phabricator.kde.org/D25982
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=415048
--- Comment #1 from David E. Narvaez ---
If I understand correctly you are reporting that BoostPython is not found when
all you have is Python 3, right? If that is the case, I believe it is by design
since the Python scripting interface has not been ada
