We have a job that creates a python virtualenv, then installs our dependencies into it. How do we ensure that each subsequent step in that job uses the same virtualenv? I seem to remember circleci 1.0 had a special file you could add extra env things to at build time, but I can’t see any reference to this in the 2.0 docs.
At the moment it seems the only alternative is to source the virtualenv’s activation script in every step, but that’s a bit frustrating. Are there any suggested workarounds?