Comment #12 on issue 480 by pekka.klarck: New installation and start-up
system
http://code.google.com/p/robotframework/issues/detail?id=480
Getting back to the limitation in issue 1054: The problem with the new
installation system on virtualenv is that, as mentioned in the previous
comment, the created pybot script just executes `python -m robot.run "$@"`
which obviously runs the python that happens to be in PATH.
Good news:
As mentioned in the previous comment, pybot script is nowadays just
convenience over `python -m robot.run`. Running that command o that you
replace `python` with path to the Python version on your virtualenv works
fine. Alternatively you can add the virtualenv Python to PATH before the
global Python or edit the pybot script manually.
Bad news:
I don't have any idea how to solve this problem automatically during
installation. Automatically updating the script would give us same problems
that the old installation system has and basically would bring us back to
the drawing board.
Proposal:
My proposal is that we keep the installation system as it is and just
document the limitation on virtualenv on installation instructions. I am,
obviously, highly interested if someone has an idea how to solve this
problem otherwise.
