Hacker News Reader

Comment by kot-behemoth | Hacker News Reader

Well, apart from Fabric.

You may want to check out Invoke (https://github.com/pyinvoke/invoke); it's the successor to Fabric, and it's Python 3 compatible.

HN appended that link: https://github.com/pyinvoke/invoke

For what I can see, Invoke is just a revamped version of Fabric’s task running components. Fabric 2.0 will "leverage Invoke for task running, leaving Fabric itself much more library oriented".

Fabric is on the way. Paramiko, the ssh library underlying Fabric, now has a Python 3 PR for which all tests pass: https://github.com/paramiko/paramiko/pull/233

Fabric isn't part of Django. There is nothing specific about Django in Fabric. In fact, the vast majority of my deployments do not use Fabric.

Do you use something in place of Fabric?

Paramiko could be a good example i think...

I was thinking something more like ansible.

Of course I'm partial to my new pave project: https://bitbucket.org/mixmastamyk/pave It is based on fabric, and uses a yaml file to automate it.

No, no, fabric uses paramiko as the ssh abstraction layer.

I am aware of that, but I still consider it one of my favorite libraries, and thought it would be useful to mention that it's not yet py3k-ready. I can imagine quite a few people might depend on it. What are you using instead?

And reportlab

Last I looked reportlab doesn't even use new-style classes.

Reply on news.ycombinator.com