On Thu, Jan 29, 2015 at 1:18 PM, Chris Barker <chris.barker@noaa.gov> wrote:
So does that mean it could be fixed in 2.* ? (or already has been?)

That it hasn't been fixed by now suggests that the core developers felt it would break more than it would repair. Might be worth scanning the relevant tracker issue(s) or searching the python-dev list archives.