Looks like this may be broken for lsf 9.1

[Pete-C]

root@farm3-srv1:/tmp/platform-python-lsf-api-master# python setup.py build
running build
running build_py
running build_ext
root@farm3-srv1:/tmp/platform-python-lsf-api-master# python setup.py install
running install
running build
running build_py
running build_ext
running install_lib
copying build/lib.linux-x86_64-2.7/pythonlsf/lsf.py -> /software/python-2.7.3/lib/python2.7/site-packages/pythonlsf
byte-compiling /software/python-2.7.3/lib/python2.7/site-packages/pythonlsf/lsf.py to lsf.pyc
running install_egg_info
Removing /software/python-2.7.3/lib/python2.7/site-packages/platform_python_lsf_api-0.0.1-py2.7.egg-info
Writing /software/python-2.7.3/lib/python2.7/site-packages/platform_python_lsf_api-0.0.1-py2.7.egg-info
root@farm3-srv1:/tmp/platform-python-lsf-api-master# python
Python 2.7.3 (default, Jun 11 2013, 13:21:10)
[GCC 4.6.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.

from pythonlsf import lsf
Traceback (most recent call last):
File "", line 1, in
File "pythonlsf/lsf.py", line 26, in
_lsf = swig_import_helper()
File "pythonlsf/lsf.py", line 18, in swig_import_helper
import _lsf
ImportError: No module named _lsf
quit()

:(

[tmetsch]

Are there any *.so file create during the build?

[Pete-C]

Hello, many thanks for your rapid reply. We do see the following .so created:
./build/lib.linux-x86_64-2.7/pythonlsf/_lsf.so

Pete

---

From: tmetsch notifications@github.com
To: tmetsch/platform-python-lsf-api platform-python-lsf-api@noreply.github.com
Cc: Pete-C pete_doh_clapham@yahoo.co.uk
Sent: Friday, 2 August 2013, 10:25
Subject: Re: [platform-python-lsf-api] Looks like this may be broken for lsf 9.1 (#6)

Are there any *.so file create during the build?
—
Reply to this email directly or view it on GitHub.

[tmetsch]

okay could be that you just need to set PYTHONPATH (pointing to the _lsf.so dir) and LD_LIBRARY_PATH. can you check that?

[Pete-C]

Hello,

apologies for the delay, manic summer. Sadly this isn't the issue. The LD_LIBRARY_PATH is all set correctly
Pete

[tmetsch]

:-D

Hmm, weird! How does it look like? And is the PYTHONPATH extended too?