When it comes to finding which packages need to be ported:
I've been disappointed by the "Python 3 Wall of Superpowers" and the fact that they've basically never updated their package list. (They update the Python 3 readiness, but you'd never find out if a popular package created in the last 4 years was incompatible, or if packages on the list have become unpopular.)
Today I found py3readiness.org, which is much more relevant and up-to-date. It has a better call to action, too.
Unfortunately, just because a package has supposedly been "ported" to Python 3 doesn't mean it works properly. I've found, reported, and developed workarounds for bugs in two of the packages shown in green on py3readiness.org.[1] Bugs that should have been found years ago if the package was being heavily used.
Both lists should replace python-ldap with ldap3. The former is abandon-ware and will never (probably) be upgraded. The latter already works great with python 3 (and is a better library all-around).
We know about that. Many of the packages are overriden if there are drop-in replacements like PIL -> Pillow.
In above list, these are not drop-in replacements and it will require lots of changes in your application code if you want to use them. One idea is to show alternative packages https://github.com/chhantyal/py3readiness/issues/9
I've been disappointed by the "Python 3 Wall of Superpowers" and the fact that they've basically never updated their package list. (They update the Python 3 readiness, but you'd never find out if a popular package created in the last 4 years was incompatible, or if packages on the list have become unpopular.)
Today I found py3readiness.org, which is much more relevant and up-to-date. It has a better call to action, too.
http://py3readiness.org/