3 ms·

I also wonder how Django not adopting it for a while is going to affect the transition as well. I realize a lot of other things are in play but Django is a big

• jnoller 16y ago
  Django has a roadmap at least.
• barnaby 16y ago
  It's not like Djangonauts are against moving to 3.x it will happen, and probably sooner/faster than you think. As for universities upgrading, it's like people who still use Windows XP and IE6. Most people have already upgraded but the long tail will stick around for a long time for no discernible reason.
  • sigzero 16y ago
    I watched the last panel where the Django core team talked. It didn't sound like it would sooner/faster than I thought it would. It will happen is about all they said.
• yummyfajitas 16y ago
  Django will be a tricky beast to port due to the fairly large ecosystem. For my web projects, I almost always use at least django, fabric, djang_extensions and django_piston. If even one of these is unavailable, I'm sticking to 2.7. I use other django libs as well, and python 3 doesn't offer me enough features to make losing those libraries worthwhile.
• ubernostrum 16y ago
  As far as I know, we're doing what the Python dev team expected for large projects: taking some time to deprecate older 2.x releases, working our way toward being 2.6- or 2.7-only, then porting from there. Nobody who actually paid attention to the Python 3 process expected this to happen quickly, or is under the impression that large projects are taking longer than expected to port.