Question: best way to address module already imported
0
Brad Langhorst • 100 wrote:
rSeqC seems to ship with it's own version of bx... but this is screwing up other stuff. What's the best approach to fix it? /mnt/galaxy/data/galaxy/galaxy-dist/lib/galaxy/__init__.py:79: UserWarning: Module bx was already imported from /mnt/galaxy/data/galaxy/sw/lib/python2.7/site-packages/RSeQC-2.3.9-py2.7-linux-x86_64.egg/bx/__init__.pyc, but /mnt/galaxy/data/galaxy/galaxy-dist/eggs/bx_python-0.7.1_7b95ff194725-py2.7-linux-x86_64-ucs2.egg is being added to sys.path self.check_version_conflict()
Hi Brad,
have you tried to run Galaxy in a virtual_env? The wiki has a good description about that.
Yes, I'm using a dedicated virtual env for galaxy already - I think the problem is that rseqc (a toolshed tool) has installed it's own local copy of bx in addition to the bx from galaxy. I bet the rseqc tool has the same warning, but the tool is not configured to be in an error state if there is stderr output.
Maybe this is an rseqc tool bug?