1. Obsolete. Either explicitly so (e.g. Google API) or abandoned, without even a minor/patch release (initools, 2010) or in some cases a code commit (e.g. pathtools, 2012) for five years or more. I suspect that they will never be Py3, the community will just move on to alternatives.
2. Working hard to bring support (e.g. ansible).
3. Part of the graphite ecosystem. If the base library won't change, none of its ecosystem will.
4. Not on public version control / issue tracking, so who knows (e.g. supervisord)
(It's not getting picked up by pypi because they haven't made a release with the trove classifier yet.)
There is a fork with Python 3 support: https://github.com/mathiasertl/fabric/
If you use fabtools, I maintain a fork of it for fabric3: https://github.com/develtech/fabtools/tree/fabric3
Also, the fabric author has been making a lot of progress on Fabric 2, which works on Python 3.
Though I would say that it's the stretch to say it might 'need no further changes' if it doesn't work with the latest version of python.
I have been using Ansible exclusively with Python 3 for over a year and only stumbled into incompatible code once, a simple case of string VS bytes literals that got quickly fixed.
python3 /usr/bin/ansible $cmd
/edit: there is actually a source for that, go figure:
there is experimental python3 support since 2.2 though.