Hi Garret, 


On Tue, Mar 3, 2020 at 8:01 AM Garret Bland <gbland@andrew.cmu.edu> wrote:
Hi All,
I tried to reinstall anaconda (Windows 10) and create a new environment to install the newest version of larch. It gave me the following error: 

conda install -yc GSECARS xraylarch
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: -
Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.
failed

Sorry for the trouble.  It seems like updating from a previous release is not working as well as I hoped.  I'm not sure what that error *really* means, but I have also seen some Anaconda environments be either very, very slow to "solve environment" or fail when I'm pretty sure it really should succeed. 

Slightly conda-specific, but: It should definitely be the case that doing an "conda update --all" or making a completely new environment and installing into that should work too.  I'm reluctant to expect most users to have to install / update with conda, but I also think it should work.

I then installed pip on my virtual environment and used pip install xraylarch. That seemed to work for me.

OK, yes.  For the Python-enabled users, `pip install xraylarch` should work for most work (including all the XAFS functionality).  It will not install some optional packages (notably tomopy), but that should be OK unless you're doing fluorescence tomography.  

Just for completeness and to prove that all three systems have their own challenges, `pip install xraylarch` will work on Windows and MacOS, but will work on Linux only if wxPython has already somehow been installed.  A binary package is not available for "Linux" and compiling from source on Linux is not trivial (these two things are related).  

Anyway, I'm glad to hear you've got something working.

--Matt