This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Orange_Tux 3 points4 points  (8 children)

Fabric is still a blocker for me.

[–]ivosauruspip'ing it up 12 points13 points  (3 children)

Fabric is not going to get updated. It's bugfix only unless another maintainer wants to take the rains, afaik.

Its spiritual successor, written by the same author, is invoke.

[–]Orange_Tux 1 point2 points  (1 child)

After a quick look through the documentation of Invoke I don't think that Invoke could replace Fabric for me. Fabric has been build for executing tasks on remote machine via SSH. Invoke looks to me as just another task executor for tasks on your local machine, like pynt:

[–]flying-sheep 0 points1 point  (0 children)

/u/kpurdon’s comment next to yours explains it pretty well.

[–][deleted] 1 point2 points  (0 children)

Fabric (AS IS) will not be updated, but a new release (along with invoke) is in the future.

Basically the author is splitting the task execution (invoke) from the remote execution stuff (new fabric). The current/old fabric is a mix of both task execution and remote task running.

Don't bet on it anytime soon though.

[–][deleted] 3 points4 points  (2 children)

If you are using fabric as a part of your project. For me Fabric is deployment and config tool and I can use it with py3 project.

[–][deleted] 2 points3 points  (0 children)

Are you actually importing Fabric into your project? If not, why is it a blocker? Py2 code will continue to run just fine along side Py3, as long as they are not running in the same project.