Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#39647 - [kdeedu-kig] Activate python support

Attached to Project: Arch Linux
Opened by Terseus (Terseus) - Thursday, 27 March 2014, 12:03 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 06 April 2014, 22:36 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Andrea Scarpino (BaSh)
Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Kig have support to write scripts in python, however this support is not activated in Archlinux.
The python support requires the boost python bindings, as we can see in the "boost" package optional dependencies the python bindings are activated for both python and python2.

To check if Kig have python support activated we can open the application, go to the menu "Objects -> Others", if the python support is activated the "Others" menu must have an item named "Python Script" as described at http://docs.kde.org/stable/en/kdeedu/kig/scripting.html

If there is no reason not to do it, please activate the python support for Kig.


Additional info:
* Observed at version 4.12.3-1
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Sunday, 06 April 2014, 22:36 GMT
Reason for closing:  Upstream
Additional comments about closing:  Report upstream and reopen if upstream thinks it's a packaging issue.
Comment by Andrea Scarpino (BaSh) - Saturday, 29 March 2014, 09:06 GMT
We don't disable it.
I just built 4.12.97 and the log clearly says that python support is enabled. But, I've not tried it yet.
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 06 April 2014, 22:35 GMT
Doesn't seem like a packaging issue to me and I don't really see what else we can do here. Report upstream and reopen if they think it's our issue.

Loading...