This PyQt4 behaviour is not appropriate. An enum should use its own values
instead of integer ones to avoid invalid entries (like values out of range) or
other kind of mistakes. It's like converting longs to integers. Sometimes it
does work but one day you will get in trouble.

I know this is marked como WONTFIX, but there's an interesting feature in the
GObject based bindings that we could implement for these cases (if not already
there):

Have the enum types as classes with a constructor that takes a integer. This
constructor would take the integer, and based on it, return the corresponding
enum object. If the enum is out of range, it generates an exception.

For instance, suppose you have in C:

// module "foo"

typedef enum {
    FOO, // 0
    BAR, // 1
    BAZ, // 2
} MyEnum;

class Foo {
    void someMethod(MyEnum x);
};

Currently the generator would only accept (I suppose, from the bug report):

import foo
f = foo.Foo()
f.someMethod(foo.MyEnum.BAZ)

My proposal would involve allowing to have:

import foo
f = foo.Foo()
f.someMethod(foo.MyEnum(2))

Here, "foo.MyEnum(2)" would return exactly foo.MyEnum.BAZ. If someone calls
e.g. "foo.MyEnum(3)", an appropriate exception would be generated.

There are some cases where allowing methods which take enums to also accept
integers, e.g. when you are doing some de-serialization and you have only the
integer value for the enum.