Le jeudi 07 octobre 2010 à 23:17 +0200, "Martin v. Löwis" a écrit :
As I said, most patches are supposed to be produced against py3k HEAD, so you could try just that as the primary heuristic.
I think this is impractical. There are tons of patches (the majority) which are in the tracker and *not* against py3k head. So this heuristics will only cover a small minority.
I don't understand what the problem is. As long as the patch *applies* cleanly on py3k HEAD, it's ok. If it doesn't, the patch will have to be re-generated anyway.
I think you may trying too hard to find smart ways of inferring the correct svn rev and branch, while developing against latest py3k is, most of the time, the required standard. Outdated patches are not really helpful anyway
Hmm. So how many versions should I go back in py3k until giving up?
Zero. Regards Antoine.