[Tracker-discuss] [issue428] Patch generator and dependent feature branches

Martin v. Löwis metatracker at psf.upfronthosting.co.za
Wed Nov 30 14:04:26 CET 2011

Martin v. Löwis <martin at v.loewis.de> added the comment:

So what do you propose should roundup do here? I propose that the current behavior is actually "correct", and that mismatches with user expectations should be dealt with by education.

For the patch generation to work in the expected manner, you could create one additional branch:

- default -> pep380pure -> pep380full
- default -> get_opinfo -> pep380full

You then submit the pep380pure branch for review, and pep380full for testing.

Alternatively, you could just do your pep380 changes on the default branch of a dedicated pep-380 clone; the patch generation can very well compare a clone's default branch with cpython's default branch.

PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>

More information about the Tracker-discuss mailing list