Apologies for the lack of changelog explanation. I agree it's not useful
and sheds zero light on why this was done.

This all came about for OpenStack. The following evaluation was done by
the upstream OpenStack community to narrow down on a single mysql
client:

https://wiki.openstack.org/wiki/PyMySQL_evaluation

At the time of that evaluation mysqldb didn't have py3 support and
pymysql did. pymysql was pure-python and supported eventlet. So pymysql
was deemed the "winning" mysql client that upstream would use.

Historically Ubuntu only supports one client in main. The reason for
that is to minimize the number of packages that get LTS/security support
provided by Canonical. So with those points in mind, we updated several
packages to move from mysqldb to pymysql. We updated all packages that
were in main that used python-mysqldb to instead use python-pymysql. The
idea was that we would no longer have packages in main that depend on
mysqldb, so mysqldb could be moved out of main and into universe.

However, today I'm not sure this is all still needed or not! python-
mysqldb and python-pymysql are still both in main and upstream OpenStack
still uses both.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699426

Title:
  Merge 4.5.1-2 from Debian Sid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-tornado/+bug/1699426/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to