>=dev-libs/glib-2.6 >=x11-libs/gtk+-2.6 >=dev-lang/python-2.2 are redundant in dev-python/gnome-python's (R)DEPEND as they are depended on by devp-python/pygtk.
They are all listed with the exact versions as given in gnome-python's RDEPEND in its configure.ac in a nice summarized list at the top. We always list exactly the dependencies as in configure.in for easy checking and updating, even the order is the same for that. This is the convention of the gnome team, and there is no real reason to start filtering out RDEPENDs that other RDEPENDs already RDEPEND upon. It would make us have to double-check in a different ebuild for every version bump to check if the dependency is high enough and that's a time waster... Like gnome-python might start to depend on glib-2.14 while pygtk is fine with glib-2.8.0 and we'd have to start checking each and every time into the pygtk build to be sure this isn't the case. So because they are explicit dependencies in gnome-python configure.in, they are also explicit dependencies in the ebuild - it matches exactly and that's a good approach. Therefore marking as WONTFIX. Thanks for the consideration.
More important, it's a gentoo semi-policy that you list all non-system deps in your ebuilds. We (gnome) extend this policy to not explicitly list X deps, since every gnome that deps on X also deps on gtk+, which deps on X, but that's the extent of our changes.