[issue5164] backport distutils 3.x changes into 2.7 when appliabl

Tarek Ziadé added the comment: I don't need a ticket for this I guess, it's done progressively -- status: open -> closed ___ Python tracker ___ __

[issue5164] backport distutils 3.x changes into 2.7 when appliabl

Martin v. Löwis added the comment: That's ok in principle, as long as you avoid committing behavioral changes along with style changes in the same change set. ___ Python tracker ___ _

[issue5164] backport distutils 3.x changes into 2.7 when appliabl

Tarek Ziadé added the comment: Unfortunately, these changes are most of the time made as small extra changes when people are working in distutils modules : they fix something, and in the same changeset, they fix a small PEP-8 issue in the area they are working on. So it seems hard to merge bac

[issue5164] backport distutils 3.x changes into 2.7 when appliabl

Martin v. Löwis added the comment: Hmm. Ok. I was hoping you could point to a revision number... ___ Python tracker ___ ___ Python-bugs-list ma

[issue5164] backport distutils 3.x changes into 2.7 when appliabl

Tarek Ziadé added the comment: PEP8 : - removing space between function names and () like: function () -> function() - function(arg1, arg2, arg3) becomes function(arg1, arg2, arg3) - remove the usage of string.translate, type(foo) is StringType

[issue5164] backport distutils 3.x changes into 2.7 when appliabl

Martin v. Löwis added the comment: What specific changes do you have in mind? -- nosy: +loewis ___ Python tracker ___ ___ Python-bugs-

[issue5164] backport distutils 3.x changes into 2.7 when appliabl

New submission from Tarek Ziadé : It's annoying to get conflicts on changes in distutils in the trunk, when forward-porting to 3.x, because other changes where made there and only there. Things like PEP8-ification and modern syntax changes needs to be backported to 2.7 when appliable to reduce t