I replaced it with Ansible when I was doing a 2 to 3 transition about a year ago. It wasn't easy, but learning a real infrastructure automation tool (which Fabric is not) was worth it.

I thought Ansible wasn't ported to Python 3 [0] and actually had a lot of weird bugs when I last tried to use it. It is one of the few reasons I keep Python 2 installed on my laptop.

[0]: http://docs.ansible.com/ansible/faq.html#how-do-i-handle-pyt...

yes, but what ansible uses in the backend is easy to forget, as you never actually have any contact to python in your yml files.

You rarely have straight dependencies on fabric from your app though. Personally I simply treat it as a command line tool, and `pip install` it system wide. It just happened to have been written in Python 2, and to require script files written in Python 2, but it's orthogonal to the apps/scripts I write with Python 3. Maybe your use case is different.

When I switched to Python 3, I used Invoke to replace Fabric. The main developer of Fabric is working on Invoke as the replacement for Fabric.