Andreas Tille <andr...@an3as.eu> writes: > the short answer is: Convincing upstream to write Python3 and removing > the 2to3 patch at all is the best way.
Meanwhile, if you do need to patch in Python 3 support, you may be able to reduce the opportunity for bitrot by doing so in the form of *two* patches: one for the formal changes 2to3 generates itself, which you can readily recreate by running that tool again, and a second for any additional changes you need to make. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu