Hi Kenneth,
Thanks for the info. I was using the GitHub tarball just from habit, going back
awhile (don’t remember original reason). And pip was was 1.61. I upgraded pip
and ran:
pip install --prefix=$EB/easybuild-2.7.0 easybuild==2.7.0"
It then installed fine. Thanks. However, invoking easybuild, I get the error
“no module named easybuild”;
work$ ls -ld $EB/easybuild
lrwxrwxrwx 1 heywood itstaffnew 15 Mar 22 09:23
/sonas-hs/it/hpc/home/easybuild/easybuild -> easybuild-2.7.0
work$ eb --version
/usr/bin/python2: No module named easybuild
work$ which python2
/usr/bin/python2
work$ module load goolf Python
work$ which python2
/sonas-hs/it/hpc/home/easybuild/install_prod/software/MPI/GCC/4.4.6/OpenMPI/1.4.5-opt-hpc/Python/2.7.6/bin/python2
work$ eb --version
/sonas-hs/it/hpc/home/easybuild/install_prod/software/MPI/GCC/4.4.6/OpenMPI/1.4.5-opt-hpc/Python/2.7.6/bin/python2:
No module named easybuild
work$
If I set PYTHONPATH, then vsc.utils is not found:
work$ export PYTHONPATH=$EB/easybuild/lib/python2.7/site-packages
work$ eb --version
Traceback (most recent call last):
File
"/sonas-hs/it/hpc/home/easybuild/install_prod/software/MPI/GCC/4.4.6/OpenMPI/1.4.5-opt-hpc/Python/2.7.6/lib/python2.7/runpy.py",
line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File
"/sonas-hs/it/hpc/home/easybuild/install_prod/software/MPI/GCC/4.4.6/OpenMPI/1.4.5-opt-hpc/Python/2.7.6/lib/python2.7/runpy.py",
line 72, in _run_code
exec code in run_globals
File
"/sonas-hs/it/hpc/home/easybuild/easybuild-2.7.0/lib/python2.7/site-packages/easybuild/main.py",
line 47, in <module>
from easybuild.tools.build_log import EasyBuildError, init_logging,
print_msg, print_error, stop_logging
File
"/sonas-hs/it/hpc/home/easybuild/easybuild/lib/python2.7/site-packages/easybuild/tools/build_log.py",
line 39, in <module>
from vsc.utils import fancylogger
ImportError: No module named vsc.utils
work$
Ideas?
Thanks,
Todd
From:
<[email protected]<mailto:[email protected]>> on
behalf of Kenneth Hoste <[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
List-Post: [email protected]
Date: Monday, March 21, 2016 at 5:59 PM
To: "[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
Subject: Re: [easybuild] [ANN] EasyBuild v2.7.0
Hi Todd,
This is a side-effect of a check that is in place in easybuild/__init__.py.
Because of using declare_namespace in the __init__.py files, running
'eb' from the directory where easybuild/__init__.py is located may yield
strange 'import' errors, so we put a check in place that spits out a
clear error message.
However, it seems that pip is triggering this too, that's unfortunate...
I'll see if we can get around that somehow, without running into the
import errors.
A couple of questions for you:
* which version of pip are you using here?
* is there any particular reason why you're grabbing the tarball for the
master branch from GitHub, rather than installing through PyPI (the
usual way things are installed with pip), i.e.:
pip install --install-option "--prefix=$EB/easybuild-2.7.0"
easybuild==2.7.0
Note that since pip 8.0.0, the --prefix option is supported 'directly',
i.e. this should also work:
pip install --prefix=$EB/easybuild-2.7.0 easybuild==2.7.0
regards,
Kenneth
On 21/03/16 15:58, Heywood, Todd wrote:
It look like the PyPI installation method via pip no longer works:
eb_install$ pip install --install-option "--prefix=$EB/easybuild-2.7.0"
http://github.com/hpcugent/easybuild-framework/archive/master.tar.gz
Downloading/unpacking
http://github.com/hpcugent/easybuild-framework/archive/master.tar.gz
Downloading master.tar.gz (unknown size): 1.4MB downloaded
Running setup.py egg_info for package from
http://github.com/hpcugent/easybuild-framework/archive/master.tar.gz
ERROR: Running EasyBuild from /tmp/pip-SXlmFZ-build does not work (Python
packaging weirdness)...
Complete output from command python setup.py egg_info:
ERROR: Running EasyBuild from /tmp/pip-SXlmFZ-build does not work (Python
packaging weirdness)...
----------------------------------------
Cleaning up...
Command python setup.py egg_info failed with error code 1 in
/tmp/pip-SXlmFZ-build
Storing complete log in ~/.pip/pip.log
eb_install$
Todd
From:
<[email protected]<mailto:[email protected]><mailto:[email protected]>>
on behalf of Kenneth Hoste
<[email protected]<mailto:[email protected]><mailto:[email protected]>>
Reply-To:
"[email protected]<mailto:[email protected]><mailto:[email protected]>"
<[email protected]<mailto:[email protected]><mailto:[email protected]>>
List-Post: [email protected]
Date: Monday, March 21, 2016 at 6:52 AM
To: EasyBuild
<[email protected]<mailto:[email protected]><mailto:[email protected]>>
Subject: [easybuild] [ANN] EasyBuild v2.7.0
Dear EasyBuilders,
I'm happy to announce the release of EasyBuild version 2.7.0 [1].
It's beyond any doubt that this is the best release so far, you'll see...
This is a big release, with many small and a couple of large enhancements.
Major highlights for this release include:
* stable Cray support (thanks a lot to Petar Forai and Guilherme
Peretti-Pezzi & his colleagues at CSCS for their contributions!) [2]
* detailed overview coming soon at
http://easybuild.readthedocs.org/en/latest/Cray_support.html
* improved GitHub integration:
* enhancements for --new-pr/--update-pr/--upload-test-report
* bug fixes for --from-pr
* added support for --install-github-token and --check-github
* updated detailed documentation available soon at
http://easybuild.readthedocs.org/en/latest/Integration_with_GitHub.html
* more responsive 'eb' command, thanks to enabling Python
optimization mode
* support for showing the current EasyBuild configuration using 'eb
--show-config' [3]
* better bash completion support
* bug fixes and simplified implementation for --minimal-toolchains
* correctly defining the 'easybuild' namespace (i.e. no more
'harmless' import warnings)
* this introduces the requirement for having the 'setuptools'
Python package available at runtime
* if you have custom easyblocks, make sure you're using
--include-easyblocks,
or change the __init__.py files in your custom easyblocks
directory to use 'pkg_resources.declare_namespace' rather than
'pkgutil.extend_path'
* fixed issues with using EasyBuild in an environment where
'python' is Python 3.x ('python2' must be available through $PATH in
that case)
* 6 new software-specific easyblocks, incl. MPICH
* example easyconfig files for 63 new software packages
* support for installing latest Intel compilers (2016 update 2),
Perl 5.22.1, Python 3.5.1, R 3.2.3 (w/ updated extensions), GROMACS
5.1.2, netCDF 4.4.0, etc.
... and various other enhancements and bug fixes.
More details are available in the release notes [4].
Thanks to everyone who contributed to this release in one way or another!
To upgrade to EasyBuild v2.7.0, there are several options:
(i) (re)bootstrap EasyBuild to obtain an EasyBuild/2.7.0 module to
load [5]
(ii) install EasyBuild v2.7.0 with a previous version of EasyBuild,
using the easyconfig file available in [6]
(iii) install EasyBuild v2.7.0 from PyPI, using one of the standard
Python installation tools (easy_install, pip, ...)
(iv) update your Git working copies of the different EasyBuild
repositories
Enjoy!
regards,
Kenneth
EasyBuild release manager
[1] http://pypi.python.org/pypi/easybuild
[2] https://github.com/hpcugent/easybuild-framework/issues/1390
[3]
http://easybuild.readthedocs.org/en/latest/Configuration.html#overview-of-current-configuration-show-config-show-full-config
[4] http://easybuild.readthedocs.org/en/latest/Release_notes.html
[5]
http://easybuild.readthedocs.org/en/latest/Installation.html#bootstrapping-easybuild
[6] https://github.com/hpcugent/easybuild-easyconfigs/pull/2740
