python wnck bindings have broken constants again
Bug #642913 reported by
Tony Houghton
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gnome Python Desktop |
Won't Fix
|
Medium
|
|||
gnome-python-desktop (Debian) |
Won't Fix
|
Medium
|
|||
gnome-python-desktop (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Bug 447479 got fixed in libwnck (the constants should have been registered as flags, not as enums) but a workaround also got put in to python's wnck bindings (register constants as enum instead of flags). So this has created a sort of mirror image of the original bug with effectively the same symptoms.
Fixed on natty; needs back-porting for any supported release where doing:
python -c "import wnck"
produces a warning or error.
TEST CASE:
0. install python-wnck
1. run python -c "import wnck"
2. verify what you get a WARNING
3. install python-wnck from -proposed
4. repeat (1)
5. verify that this time there is no warning
Changed in gnome-python-desktop: | |
importance: | Unknown → Medium |
status: | Unknown → New |
tags: | added: patch |
Changed in gnome-python-desktop (Debian): | |
status: | Unknown → Fix Released |
description: | updated |
Changed in gnome-python-desktop (Ubuntu Lucid): | |
status: | New → Triaged |
Changed in gnome-python-desktop (Ubuntu Maverick): | |
status: | New → Triaged |
Changed in gnome-python-desktop (Debian): | |
status: | Fix Released → Unknown |
tags: | added: testcase |
Changed in gnome-python-desktop: | |
status: | New → Won't Fix |
Changed in gnome-python-desktop (Debian): | |
importance: | Unknown → Medium |
status: | Unknown → Won't Fix |
To post a comment you must log in.
I've added fixed versions to my PPA for anyone who can't wait for the fix to be released officially.
ppa:h-realh/ppa
There are versions for lucid and maverick.