News for hackers. Stuff that matters.

A comment on Django 1.6 released. Parent comment

Re:Django 1.6 released by pydanny on Wednesday November 06, 2013 @10:15AM (#6683075)
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.
[ Parent | on HN ]
Re:Django 1.6 released by kot-behemoth on Wednesday November 06, 2013 @11:09AM (#6683363)
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?
[ Parent | on HN ]
Re:Django 1.6 released by codonaut on Wednesday November 06, 2013 @11:00AM (#6683323)
Do you use something in place of Fabric?
[ Parent | on HN ]
Re:Django 1.6 released by commixon on Wednesday November 06, 2013 @11:28AM (#6683499)
Paramiko could be a good example i think...
[ Parent | on HN ]
Re:Django 1.6 released by mixmastamyk on Wednesday November 06, 2013 @02:13PM (#6684762)
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.

[ Parent | on HN ]
Re:Django 1.6 released by tutuca on Wednesday November 06, 2013 @02:16PM (#6684773)
No, no, fabric uses paramiko as the ssh abstraction layer.
[ Parent | on HN ]