[Distutils] multiple backports of ipaddress and a world of pain

[James Oakley]

On Wednesday, February 17 12:30, Philipp Hagemeister wrote:

> Preferably, one should go fix the source to return character strings in
> the first place. Usually, this includes from __future__ import
> unicode_literals, io.open with an encoding parameter, and inserting
> unconditional decode calls when the source really is bytes.

The code in question is Django, and it seems to be good in the currently supported version. This issue only occurred in older versions. It actually surprised me that this occurred, since Django is usually quite good at ensuring unicode strings throughout the code.

-- 
James Oakley
jfunk at funktronics.ca