Skip to content

Commit

Permalink
Update FAQ: MKL 30-day trial fix
Browse files Browse the repository at this point in the history
  • Loading branch information
jhunkeler committed May 6, 2016
1 parent 2a1db07 commit d5eaf16
Showing 1 changed file with 31 additions and 0 deletions.
31 changes: 31 additions & 0 deletions source/faq.rst
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
F.A.Q.
######


After "``conda create ...``" why does "``source activate astroconda``" fail?
============================================================================

Expand All @@ -21,6 +22,36 @@ To clarify, it is impossible to execute ``source activate root``. Installing Ast
Anaconda itself to be come unstable. In addition to this, removing packages from this environment is tedious and will likely break
your Anaconda installation if you are not careful. *Reinstalling from scratch is the safest option.*

Why am I being prompted by NumPy/SciPy with a MKL 30-day trial warning?
=======================================================================

The ``root`` environment of your Anaconda installation is severely outdated (``<=2.4.0``) and suffers from a crippling bug
introduced by the ``conda-3.19.x`` package.

It is possible to verify the version of Anaconda you have by running:

.. code-block:: sh
$ conda info anaconda
The only solution is to update your Anaconda installation to the latest release:

.. code-block:: sh
$ source deactivate
$ conda update conda
$ conda update anaconda
Next, update the ``astroconda`` environment to realign your packages with the ``root`` environment:

.. code-block:: sh
$ conda update -n astroconda --all
$ source activate astroconda
After doing this, the ``mkl`` 30-day trial warning will not be displayed while importing ``numpy``, ``scipy``, or any
other package requiring ``mkl``.

How does AstroConda differ from Ureka?
======================================

Expand Down

0 comments on commit d5eaf16

Please sign in to comment.