New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ImportError: libicui18n.so.58 when importing Obspy (Anaconda) #1677
Comments
This seems to be a packaging problem by anaconda that is not related to obspy. See conda-forge/conda-forge.github.io#326 (comment):
So, |
@megies The command to install icu 56.* doesn't work.
I understand this is a zsh issue but running in bash I get:
|
Ah sorry, try this: |
It doesn't work. Trying your command doesn't work. It returns a conflict:
|
Can you try with a fresh new environment? $ conda create -n new_env python=2.7
$ source activate new_env
$ conda config --add channels conda-forge
$ conda install obspy 'icu=56.*' |
Huge problems on this end, too. I'm beginning to panic. My main system is now down after trying a "conda update obspy". Today I tried my laptop and it too, is down: I can't even launch Python or Ipython notebooks. I didn't even do any updates and it used to work just a few weeks ago! I have work to do on Monday and no operational platforms at this point. How does the fresh new environment work? Does it replace the old environment? - I'm almost afraid of trying it for fear of breaking something worse! |
@megies The problem persists. Also, though you specified using Python 2.7 (I am working with Anaconda 3) when I open Ipython I still get:
I have an export line in my zshrc which Anaconda usually puts in bashrc. @tychoaussie Are you using Anaconda?
Here's conda's docs As for this (broken) environment you might want to try to update all modules instead of a single one. This is preferred. Also precede that by updating conda:
** The idea of environment is to have different setups. Each environment is (afaik) independent of the other except for the base python installation. In other words, each environment can have different modules installed. When you have a certain environment (env for short) activated any modules that you install go into that env. If no env is activated then the installations/updates are in the main env. |
Please post the output of |
Also |
If you have an environment that doesn't have IPython installed but your root environment has IPython, your shell will start IPython in root environment. That's something you should keep in mind. I would in general advise to keep the root environment as bare as possible and only use it for handling other environments via |
Post some error messages and conda debug output as stated above and we can try to help. But we need this input to work with.. |
I can reproduce those problems with icu/matplotlib.. If I do the following:
then I'm running into problems:
Conda list for this problematic package set:
What works for me is this:
Working set of packages:
N.b.: I have conda-forge channel in my ~/.condarc
Also compare some failing CI builds in conda-forge/obspy-feedstock#6. |
/users/Daniel/.condarac contains: `ssl_verify: 'True'
C:\WINDOWS\system32>conda config --add channels conda-forge C:\WINDOWS\system32>conda config --add channels obspy C:\WINDOWS\system32>conda install obspy
Current conda install:
C:\WINDOWS\system32>conda install obspy 'icu=56.*'
Current conda install:
C:\WINDOWS\system32> |
With the patient help of Tobias Megies, I have managed to rebuild the Anaconda package, and now have revived Obspy 1.0.2. It is working now, both on command line, and within the new Anaconda Navigator's Jupyter. I have created a working environment called 'new' such that the root environment should be preserved in case I break something. In Anaconda Navigator, I activated the new environment, installed Jupyter within that environment, and then activated the Obspy channel within the navigator. Now I can run my utilities, and develop code within the web interface. On Monday I will repair my work computer, and validate our suite of utilities & data converters to make sure that they still work. In short, - Crisis seems to be over. Thanks, Tobias! |
There's also |
@QuLogic what do you think should we do pinning-wise for our conda packages in conda-forge/obspy-feedstock#6 ..? |
Just for reference.. linking this to conda-forge/lxml-feedstock#10 and conda-forge/libxslt-feedstock#8 |
This pinning was (temporarily) added. |
traceback.txt
I installed ObsPy using conda as outlined in the Wiki. When I import it I get the following error (after the tracback):
import obspy as op
or
from obspy import read
Traceback is attached
The text was updated successfully, but these errors were encountered: