Maintaining a backported module

[Ethan Furman]

On 10/23/2013 09:54 PM, Steven D'Aprano wrote:
>
> I'm looking for advice on best practices for doing so. Any suggestions
> for managing bug fixes and enhancements to two separate code-bases
> without them diverging too much?

Confining your code to the intersection of 2.7 and 3.x is probably going to be the easiest thing to do as 2.7 has a 
bunch of 3.x features.

Sadly, when I backported Enum I was targeting 2.5 - 3.x because I have systems still running 2.5.  That was *not* a fun 
experience.  :(

--
~Ethan~