Hi Judith,

On 28/01/16 22:37, Gardiner, Judith wrote:

[ruby01]$ eb --version

/usr/local/easybuild/2.6.0/software/EasyBuild/2.6.0/lib/python2.6/site-packages/vsc_base-2.4.16-py2.6.egg/vsc/__init__.py:29: UserWarning: Module vsc was already imported from /usr/local/easybuild/2.6.0/software/EasyBuild/2.6.0/lib/python2.6/site-packages/vsc_base-2.4.16-py2.6.egg/vsc/__init__.pyc, but /usr/local/easybuild/2.6.0/software/EasyBuild/2.6.0/lib/python2.6/site-packages/vsc_install-0.9.12-py2.6.egg is being added to sys.path

  import pkg_resources

/usr/local/easybuild/2.6.0/software/EasyBuild/2.6.0/lib/python2.6/site-packages/vsc_base-2.4.16-py2.6.egg/vsc/__init__.py:29: UserWarning: Module easybuild was already imported from /usr/local/easybuild/2.6.0/software/EasyBuild/2.6.0/lib/python2.6/site-packages/easybuild_framework-2.6.0-py2.6.egg/easybuild/__init__.pyc, but /usr/local/easybuild/2.6.0/software/EasyBuild/2.6.0/lib/python2.6/site-packages/easybuild_easyblocks-2.6.0-py2.6.egg is being added to sys.path

  import pkg_resources

This is EasyBuild 2.6.0 (framework: 2.6.0, easyblocks: 2.6.0) on host ruby01.osc.edu.



First of all, these warnings are harmless in the sense that everything will work even though they are being spit out.
I agree they are ugly though, and we should try and get rid of them.

The problem is that vsc-base was split up recently, into what vsc-base is now and vsc-install, which provides support for installing/testing vsc-* packages.

This implies that the 'vsc' namespace is spread across two different directories now, and that "import vsc" in Python will result in reading vsc/__init__.py from two different places. Python (or setuptools?) thinks this is weird, and throws the warnings.

Same applies to the 'easybuild' namespace, which is imported from two locations (framework & easyblocks).

This is a well known issue, and there are workaround to just silence the warning [1,2], but that's probably not the best way to 'fix' this issue.

We're actually getting it too on our systems, but not consistently, it depends on how you install EasyBuild (an I *think* also on the version of setuptools, but I'm not sure about that).

I've opened an issue on this in the EasyBuild framework repository on GitHub [3], and tagged it to try and fix this by the next EasyBuild release.


regards,

Kenneth

[1] http://stackoverflow.com/questions/7239518/module-pytz-was-already-imported [2] http://stackoverflow.com/questions/3861336/how-do-you-correct-module-already-loaded-userwarnings-in-python
[3] https://github.com/hpcugent/easybuild-framework/issues/1588

Reply via email to