Skip to content

Commit

Permalink
better solution for cleaning numba cache
Browse files Browse the repository at this point in the history
  • Loading branch information
yalinli2 committed Nov 5, 2024
1 parent 7e6b99d commit b494632
Showing 1 changed file with 2 additions and 4 deletions.
6 changes: 2 additions & 4 deletions docs/source/FAQ.rst
Original file line number Diff line number Diff line change
Expand Up @@ -77,17 +77,15 @@ There are multiple possible reasons:
Then when you open the Jupyter Notebook, select the ``<KERNEL NAME>`` kernel when you create a new notebook you can find more details in this post about `enabling multiple kernels in Jupyter Notebook <https://medium.com/@ace139/enable-multiple-kernels-in-jupyter-notebooks-6098c738fe72>`_.


``Underlying object has vanished``
``underlying object has vanished``
**********************************
This error is related to ``numba`` caching, we haven't figured out the exact mechanism, but clearing cache will help resolve it. One/both of the following approaches should work:

1. Clear cache. Remove all ``.pyc``, ``.nbc``, and ``.nbi`` files, you can do this in your CLI using (replace <DIR> with the directory to your ``thermosteam``, ``biosteam``, ``qsdsan``, and ``exposan`` directory):

.. code::
get-childitem <DIR> -recurse -include *.pyc | remove-item
get-childitem <DIR> -recurse -include *.nbc | remove-item
get-childitem <DIR> -recurse -include *.nbi | remove-item
get-childitem . -recurse -include *.pyc, *.nbc, *.nbi | remove-item
2. Uninstalling and reinstalling a different version of ``numba``. Suppose you now have 0.58.1 and the newest version is 0.60.0, you can do:

Expand Down

0 comments on commit b494632

Please sign in to comment.