taking a stronger stance on the python bugs

[Aaron J. Seigo]

hi...

so dozens of python bindings related crashes have been languishing in plasma's 
bugs list. i'm currently dealing with them by:

* invalidating ones that are invalid (e.g. crashing in the nvidia blob) and 
closing ones that were fixed because the bug was actually in libplasma and 
since fixed. this is the minority

* forwarding unique looking backtraces to the bindings components in bugzilla

* closing the non-unique-looking ones as upstream

i understand that there's a gsoc project to improve the python bindings in kde 
and that's great news. however, it isn't a binding that the plasma team 
maintains, nor is it the bindings we recommend by default. as there is very 
little we can do about it ourselves, i'd like us to adopt a "hard line" policy 
on such bug reports so they don't continue to take up space in our bug 
listings for no reason: forward new problems to bindings, close the rest 
without prejudice.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/plasma-devel/attachments/20110527/3a5c0805/attachment.sig