Comment #5 on issue 236 by pekka.klarck: system path appears to not be
updated if installing RF in virtual-env on Mac OSX
http://code.google.com/p/robotframework/issues/detail?id=236
I investigated this further and think I found the root cause for the
problem. It
seems that 'distutils.sysconfig.get_python_lib' returns
'/Library/Python/2.5/site-packages' both when using the default Python
installation
and when on virtualenv. Searching "virtualenv get_python_lib" gave some more
information (e.g. [1] and [2]) and it even seems that in virtualenv 0.9.2
'get_python_lib' has been patched "to point to the global locations" [2].
[1]
http://bitbucket.org/dhellmann/virtualenvwrapper/issue/3/add-pydir-macro-for-handy-functionality
[2] http://pypi.python.org/pypi/virtualenv
The underlying problem is related to on how pybot, jybot and rebot scripts
are
updated during the installation to contain correct paths to Python/Jython
executable
and Robot Framework installation directory. The original system is slightly
hackish
and how we added a support to easy_install was definitely a kludge (see
setup.py and
robot_postinstall.py for details). To support both virtualenv and
easy_install we
needed to find out a reliable way to get a path to 'site-packages' under
virtualenv
but I couldn't figure out any. I'm actually a bit surprised that this
worked for
Janne on Linux and wonder could it be that in his case the system picked up
pybot
script from an old installation. Should retest with RF uninstalled
altogether.
I don't have any further ideas on how to fix this other than changing the
whole
installation procedure (which we definitely will do when Jython supports
normal
installation). Because installing RF from the source distribution works with
virtualenv the easy_install problem isn't that severe. My current plan for
handling
this issue in RF 2.1 is just updating installation instructions so that
they mention
that installing with virtualenv + easy_install doesn't work. Help fixing
the actual
problem is of course highly appreciated!
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
