Another way would be to allow the user to specify a custom worker (instead of a customer worker script). This would tie in elegantly with our plan of supporting different kinds of workers (https://github.com/nvie/rq/issues/45), as well as allowing the user to add in their own pre/post job execution hooks (https://github.com/nvie/rq/issues/233) as necessary. 

Implementation wise, we can specify a worker class in the config file (or through command line):

```
[Worker]
class='path.to.MyWorker'
```

The worker class would look something like:

```python
class MyWorker(ForkingWorker):

    def pre_fork(self):
        # code here

    def post_fork(self):
        # code here
```

Thoughts?