Hello EasyBuilders,
One of the important changes that was planned for EasyBuild v2.0 is to
start using the vsc-base library as a proper dependency, rather than
copy-pasting its code into the EasyBuild framework codebase itself.
Just last week, the pull request implementing this has (finally) been
merged into the develop branch of the easybuild-framework repository
(see https://github.com/hpcugent/easybuild-framework/pull/1160).
This basically involved removing all .py files under the 'vsc'
subdirectory, but unfortunately some residual stuff may be left behind
in your git working copy of easybuild-framework, i.e. compiled Python
code in the form of .pyc files.
Since these files are not tracked by git (because they are listed in
.gitignore) and git does not track (empty) directories, we can not
enforce that these files are cleaned up when you update your git working
copy (at least, I'm not aware of a way to do so).
To clean up your working copy of easybuild-framework, just simply remove
the entire 'vsc' subdirectory, after making sure no .py files remain in
there.
Subsequently, you will need to make vsc-base available in one way or
another: either by installing it from PyPi, or by cloning the vsc-base
repository that resides at https://github.com/hpcugent/vsc-base, and
including <prefix>/vsc-base/lib (note: the 'lib' *subdirectory*) into
$PYTHONPATH.
This is mainly of concern to those of you who are working with a
'development setup' of EasyBuild.
If you are installing EasyBuild using a Python installation mechanism
(easy_install, pip, setup.py, etc.) you should not be affected by this.
The updated setup.py script (which is used by easy_install/pip/etc.)
properly specifies that vsc-base must be pulled in/updated from
https://pypi.python.org/pypi/vsc-base as a dependency.
The (develop) documentation still needs an update with respect to this
in a couple of places, I hope to tackle that ASAP.
regards,
Kenneth
- [easybuild] import change in EasyBuild framework for develo... Kenneth Hoste
-
