Comment 4 for bug 1094230

I vote for prioritizing it low enough that we don't start on it until after April 2015, at which point we can close it out as only affecting unsupported Python versions.

I mean, Lucid's got support through April 2015 and then it's done, so the two Ubuntu LTSes will be Precise and Trusty, both of which have Python 2.7, plus RHEL 7 has Python 2.7, so that'll be it. Plus, the Python team has said that 2.6 is EOL, so no more updates for anything at all ever.

I guess if someone wants to take a crack at fixing it in Swift for 2.6 I'm not going to stop them, but it's super-duper-low-priority to me.