Page History

...

Each package should be installed inside user's virtual environment - this way, it will be possible to provide users with any version of actor and Python workflow will be composed of loosely coupled actors.

Sample structure of the actor can be found here: /gss_efgw_work/work/g2michal/cpt/development/python_modules/simple 

Inside, we have a sample structure of Python module with native code: demo.c.

src/
|-- actor_demo
|   |-- __init__.py
|   `-- sample.py
|-- demo.c
`-- setup.py

In this scenario, actor is treated as package. It means, we can install it using pip command. This approach provides huge flexibility when it comes to distributing actors. It's very easy to create virtual environment and install actor inside it.

> virtualenv --no-site-packages -p /usr/bin/python2.7 sample
> source sample/bin/activate.csh
> pip install --upgrade --force-reinstall ./src/
> python test.py
Hello from fun
Hello World!

This way, it's possible to create custom work environments where various actors can be installed, reinstalled, where we can mix different versions of actors.

One common installation of actor resources

...