:thumbsup:

I'm not sure about this change, is it really needed?

This should not be, since celery would be installed in the virtualenv, wouldn't it?

Or in this case since it's vagrant, in the VM itself

The celery binary is referenced in /usr/bin, but celery is only ever installed from the requirements to the environment. So, how does it end up in usr/bin?

It'll be /usr/bin/celery-3 for Python 3 on the system anyway.

I couldn't find celery-3 in usr/bin, probably because we didn't install python3-celery in the VM.

It is only installed from requirements.txt into the environment, so we can probably use that path instead.

I'm not sure how it ended up in usr/bin for the f25 python2 setup or in usr/local/bin this time

So we should set this to the celery binary in the virtualenv, right?

This looks good to me, let's rebase and get it in :)

@akanksham Are you able to rebase this so @pingou can merge this?

@akanksham do you think you could rebase one more time, it has one small conflict, nothing major.

This way you and @alexgleason may be able to test it one more time before we get it in :)

Sure, it seems to be working fine.