Being from Wisconsin, I always get called out for how I pronounce "bag" and "bagel".

From Minnesota. I get the same.

I had the same thing happen to me.

I feel like I relearn this lesson at least once a month.

Couldn't help but think the same thing as I read this.

EDIT: Title changed from "Why Python 3 Isn't Being Used More" to "Problems With the Python 3 Ecosystem"

Ubuntu is one the most deployed server distributions of linux, and one of the most battle tested. While this post isn't meant to criticize python 3 (I think the language is perfectly fine as is), it's meant to criticize the ecosystem, where one of the most deployed distributions doesn't work.

Yes, but Debian is also very widely deployed and doesn't ship with a broken Python 3 package. I'm just pointing out that your issue is specifically related to Ubuntu. You'd be better off calling your article: Ubuntu is Not A Suitable Platform for Python 3 Development, or something along those lines.

The issue linked was against jessie/sid. Debian users expect broken things outside of stable.

The Ubuntu release in question was the LTS Ubuntu.

CentOS is arguably the most deployed server distribution of Linux, and it (RH) ships a perfectly fine python3 via SCL.

Ubuntu is a snapshot of Debian unstable, and it's not surprising that shipping cutting edge packages results in a few that are broken.

Perhaps the title should be altered. My main argument is that the ecosystem around python3 is what's holding it back. I think the language itself is perfectly ready, and even most major packages have been ported over.

Check out https://python3wos.appspot.com/ . The majority of major packages have been ported over. Most of the bigger stuff is often run independently and not actually imported by other code (sentry, supervisor, ansible... to name a few).

This is awesome

More modular? I think how modular it is, is one of Django's greatest strengths. Don't like django's templating? You can be up and running with jinja2 in less than 20 lines. Don't like Django's user model? Substitute your own, or if you just need a different auth backend, write your own. Have a desire to use a less common DB? Write a db backend. As far as trashing the ORM for SQLAlchemy, there are a number of django packages that aim to do just that.

There is a small number of ways I could imagine Django being MORE modular.