[Twisted-Python] [RFC] Introducing six as a dependency

Antoine Pitrou solipsis at pitrou.net
Thu Jul 26 12:49:59 EDT 2012

On Thu, 26 Jul 2012 17:55:50 +0200
Vladimir Perić <vlada.peric at gmail.com> wrote:
> Hello all,
> as part of my work on porting Twisted to Python 3, I have considered
> using the six library[1] to help with some issues. six is basically a
> compatibility library - same idea as our twisted.python.compat module.
> Now, one approach is to add six as a dependency of Twisted - it is a
> very small library so hardly a problem; on the other hand, it is an
> additional dependency. The other approach would be to copy the
> required code over to the t.p.compat module (six' license[2] is
> basically "do what you want with this code"), but this is additional
> work and we might miss out on the eventual bugfix (though there has
> only been a couple since the project started).

Copying them sounds like the saner approach to me. These
compatibility wrappers are unlikely to change significantly, and
requiring a dependency on such a small module is not very helpful.

If you really want to minimize maintenance, you can also ship six as a
twisted.python submodule, and synchronize the copy when there are
interesting bug fixes.



Software development and contracting: http://pro.pitrou.net

More information about the Twisted-Python mailing list