-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relative path in $file.link not relative to position of file #2
Comments
@dagg, That fixes it. FYI, there are some additional print statements HELLO On Wed, Jun 26, 2013 at 4:12 AM, Dag Sverre Seljebotn <
|
I take that back. There is still something strange going on. When I use the [minikees:
On Thu, Jun 27, 2013 at 11:04 AM, Chris Kees [email protected] wrote:
|
Several guys at my lab are trying to use hashstack on various versions of mac os x, and we are all still getting this behavior where sys.path is not set correctly if we put the development profile bin dir in our path. @dagss I'm not sure it's a launcher problem, or at least as far as I can tell launcher is extracting precisely the same information in both cases based on the debugging output You can see below (os x 10.7 machine) that the only difference is whether python is called with the full path or letting the shell resolve it. Using the full path results in the correct sys.path, otherwise sys.path points to the python artifact, which contains no packages: kees:~ buildbot$ python -c "import sys; print sys.path" kees:~ buildbot$ which python |
@cekees , I believe this commit should fix the issue you mentioned in email with relative paths not working in
local/bin/python.link
. Will wait for your verification before closing. (I didn't push it to python-hpcmp2 yet, so put the commit hash below into packages.yml)1ae1868
The text was updated successfully, but these errors were encountered: