6 ms·

It's been heart breaking after putting so much effort myself into working on python3 stuff to see the Django people, and the other big slow python framework...

• ebtalley 16y ago
  I can sympathize but I also see those with a need for the stability that comes with long term support. Django has reached a level of acceptance like Debian, or CentOS where intensive refactors are unacceptable. Maybe it's up to someone else to fork Django.
• jacobolus 16y ago
  One problem for Django and similar projects is that many hosted systems, etc., still only run 2.3 or 2.4, and they don’t want to cut those people off for as long as they can. As far as I know it’s rather difficult to write code that works on both 2.3/2.4 and 3.x, since the 2to3 tool assumes a recent 2.x version.... so my understanding is that they’re phasing out one python version or so each release, with the hopes of eventually getting to a 2.6+/3.x release. I don’t think they’re really “ignoring” Py3k. Then again, I’m not really an expert.
  • illumen 16y ago
    It's not that hard to support 2.4-3.1 with the same code base. It's been done, and documented by a bunch of projects now.