On Sunday 21 September 2008 06:24:50 Martin Pitt wrote: > Alberto Milone [2008-09-19 20:30 -0000]: > > Yes, the contents of jockeyKde (i.e. 2 .py files) are generated > > automatically at build time. They are real modules which are imported by > > jockey-kde. > > > > Moving jockeyKde into kde/ (in the source code) wouldn't be a problem. > > Great. > > ... > > If you prefer, I can get rid of them by calling /usr/bin/pykdeuic4 with > > subprocess in setup.py, it wouldn't be as elegant though (I couldn't > > check exceptions in case of malformed .ui files, etc.). > > Doesn't pykdeuic4 provide error handling/reporting as well? I'd rather > not keep duplicated code in jockey if we can avoid it in any way. > Build tools like those are prone to change over time and should really > be kept centralized. >
Ok, the result is in revision 381. NOTE: currently I have to call pykdeuic4 with Python because calling it directly triggers a bug: $ pykdeuic4 bash: /usr/bin/pykdeuic4: Permission denied Maybe this should be discussed in another bug report. Alberto -- KDE interface fails to start: No module named kurllabel https://bugs.launchpad.net/bugs/271935 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
