Here we track bugs with a verified and working Python 3 patch that is ready to be pushed.
This where the packager is either allowing someone else to push the patch, or where they've been asked to review and push the patch but have not responded in a given time frame.
Shouldn't the dependency relation of this and PY3PATCH be the other way around?
I'm not entirely sure.
(In reply to Miro Hrončok from comment #1)
> Shouldn't the dependency relation of this and PY3PATCH be the other way
> I'm not entirely sure.
I see it thus: First there needs to be a patch for the package and only then can we push it. Therefore the non-existence of patches blocks us from pushing the patches. Hence PY3PATCH blocks PY3PATCH-PUSH.
However, I'm certain there are other ways of looking at it.
Please use pull requests and CC any of these people if you need a patch pushed:
churchyard, cstratak, torsava