Message3799
The installer currently hardcodes JYTHON_HOME in the script runner. This
makes the jython executable portable to other paths (which is the point)
-- but this breaks virtualenv
We need to work like CPython in that the executable needs to detect what
looks like a surrounding JYTHON_HOME and use that instead. virtualenv
takes advantage of this by copying sys.executable to an entirely
different HOME
We probably need the installer to hardcode something like a
JYTHON_INSTALLED_HOME -- to be used as a last resort if the CPython like
search fails
The responsible code in CPython seems to be Modules/getpath::calculate_path |
|
Date |
User |
Action |
Args |
2008-11-21 19:35:47 | pjenvey | set | recipients:
+ pjenvey |
2008-11-21 19:35:47 | pjenvey | set | messageid: <1227296147.71.0.203322860238.issue1180@psf.upfronthosting.co.za> |
2008-11-21 19:35:47 | pjenvey | link | issue1180 messages |
2008-11-21 19:35:46 | pjenvey | create | |
|