Yes, and I should make an issue about this. If we are using `@local` and `@vectorize` functions that contain `numpy.*`, `np.*`, or `whatever.*` calls. Then it is called as `numpy.*`, `np.*`, or `whatever.*` verbatim on the engines.

On the engines we [`import numpy`](https://github.com/enthought/distarray/blob/master/distarray/client.py#L96) (because importing using `import foo as bar` syntax is not supported by `IPython.parallel`'s `sync_imports` function.)

So if we want to use `@local` to replace `Context._execute` in future, as suggested in issue #22 we should always be using `numpy`, not `np'. Since `np` is not available  on the engines.