Maintaining a backported module
Antoon Pardon
antoon.pardon at rece.vub.ac.be
Thu Oct 24 03:00:24 EDT 2013
Op 24-10-13 06:54, Steven D'Aprano schreef:
> As some of you are aware, I have a module accepted into the standard
> library:
>
> http://docs.python.org/3.4/library/statistics.html
>
> I'm now at the point where I wish to backport this module to support
> versions of Python back to 3.1 at least and possibly 2.7, and put it up
> on PyPI.
>
> 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?
>
> Other than "Avoid it" :-)
I would use only one code-base and make a branch for the 2.7 version.
You can then adapt the 2.7 version where really necessary but in general
just merge adaption made in the main branch to the 2.7 branch.
I am assuming you are using some kind of version control.
--
Antoon Pardon
More information about the Python-list
mailing list