> Fred L. Drake, Jr. <fdrake@acm.org> added the  comment:

> 
> People working on this should probably also look at how  zc.buildout's 
>zc.recipe.egg handles script generation.  It's similar to  setuptools in that 
>"console_script" entry points are used, but it binds in the  desired Python 
>executable as well.
> 
> (If you ran the build with an  unversioned Python executable name, that's what 
>you get, but if you use a  versioned path, it's  retained.)

And also consider what happens when a script is installed into a virtual env, 
when the virtual env's executable *has* to be used.