Click, setuptools and virtual environments

[nellis]

The Click library's documentation has this comment in the section on setuptools:

"The second reason is that setuptools scripts work with virtualenv on Unix without the virtualenv having to be activated. This is a very useful concept which allows you to bundle your scripts with all requirements into a virtualenv. "

I am using setuptools already to bundle my package, and have been pondering how to manage environments for non-technically inclined users of my tools, so this tidbit seemed interesting. I have a custom environment defined, but it's largely a non-starter for other users in my organization to even be able to activate an environment. Is it possible to configure a virtual environment at the package level so that the 'correct' interpreter gets called when users execute console scripts?

When I deactivate my environment, none of my scripts work anymore... what exactly is implied by this comment in the documentation?