Browse files

Reword how @task helps with namespaces

  • Loading branch information...
1 parent 7b1f568 commit cb4461cbbaf18d3f50a771f535c71ec10fed5cf0 @bitprophet bitprophet committed Jun 7, 2011
Showing with 4 additions and 4 deletions.
  1. +4 −4 docs/usage/execution.rst
@@ -102,10 +102,10 @@ and enable some programming best practices, specifically:
for much more sensible code reuse than passing around simple function
objects. The classic style of task declaration didn't entirely rule this
out, but it also didn't make it terribly easy.
-* **Namespaces**. Without an easy way to tell tasks apart from other non-task
- callables, recursive namespace creation would be difficult if not impossible
- (imagine having your "task list" cluttered up with the contents of ``os.sys``
- for example.)
+* **Namespaces**. Having an explicit method of declaring tasks makes it easier
+ to set up recursive namespaces without e.g. polluting your task list with the
+ contents of Python's ``os`` module (which would show up as valid "tasks"
+ under the classic methodology.)
With the introduction of `~fabric.tasks.Task`, there are two ways to set up new tasks:

0 comments on commit cb4461c

Please sign in to comment.