Common Problems

Common Problems#

Here you will find some quick fixes for common problems and errors

Problems with Python and its Installation#

“The term import is not recognized…”

It is likely that Python code is being run in the terminal and not in the Python interpreter. To fix this, run the code in the Python interpreter either by running python in the terminal or by running the code in a Python script.

Example#
% import "module_name"
import: The term import is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

% python
Python 3.9.7 (default, Sep 16 2021, 16:59:01) [MSC v.1916 64 bit (AMD64)] :: Anaconda, Inc. on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import "module_name"
>>>
“unable to initialize device PRN”

It is likely that Python code is being run in the terminal and not in the Python interpreter. To fix this, run the code in the Python interpreter either by running python in the terminal or by running the code in a Python script.

Example#
% print("Hello, World!")
unable to initialize device PRN

% python
Python 3.9.7 (default, Sep 16 2021, 16:59:01) [MSC v.1916 64 bit (AMD64)] :: Anaconda, Inc. on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> print("Hello, World!")
Hello, World!
>>>
“urllib2.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]…”

This is likely due to missing certificates in the Python installation.

To fix this:

  1. Open Finder or file browser press the Apps or Applications folder to the left.

  2. Find the Python 3.X folder.

  3. Locate the file name Install Certificates.com and and press it, it will quickly run a terminal command to install the certificates.

(Optional) Another fix could be to install the certifi package from pip by running pip3 install certifi in the terminal.

Local TeX Live (2023) is older than remote repository (2024)

This is due to the TeX Live version being outdated. To fix this reinstall TeX Live with the latest version.

Getting requirements to build editable did not run successfully

This is likely due to corrupt files inside the folder. To fix this remove the corrupt files and try again.

“Error loading webview: Error: Could not register service workers: InvalidStateError: Failed to register a ServiceWorker: The document is in an invalid state”

This problem is likely due to the Visual Studio Code cache. To fix this, clear the cache by follwing the steps below:

  1. Close VSCode and kill any background processes running in the task manager.

  2. Go to the file explorer and to the path C:Users<user_name>AppDataRoamingCode and clear the contents of the folders Cache, CachedData, CachedExtensions, CachedExtensionVSIXs (if this folder exists) and Code Cache.

  3. Restart VSCode.

  1. Close VSCode and kill any background processes running in the task manager.

  2. Go to the file explorer and to the path /Users/<user_name>/Library/Application Support/Code and clear the contents of the folders Cache, CachedData, CachedExtensions, CachedExtensionVSIXs (if this folder exists) and Code Cache.

  3. Restart VSCode.

  1. Close VSCode and kill any background processes running in the task manager.

  2. Go to the file explorer and to the path /home/<user_name>/.config/Code and clear the contents of the folders Cache, CachedData, CachedExtensions, CachedExtensionVSIXs (if this folder exists) and Code Cache.

  3. Restart VSCode.

“OSError: [Error 86] Bad CPU type in executable: <path_to_cbc_binaries> “

This is due to Pulp complaining about bad CPU type on arm Mac as cbc (pulp dependency) doesn’t have arm binaries. This can be fixed using rosetta translation layer. Run the following command in the terminal:

/usr/sbin/softwareupdate --install-rosetta --agree-to-license
While loop getting stuck in IDLE

This is a problem native to the installation, which occur in versions of idle from 3.11.4 up till and excluding the 3.12 release (bug fixed in 3.12 and later). This can be solved by downgrading the idle version, by running the following command in the terminal:

conda install python=3.11.3
“OSError: … Error loading ….libfbgemm.dll..”

This is a Windows specific error. This happens because of a problem that is related to the released torch version and is likely due to a conflict between pip and conda. To fix this, uninstall the torch package and reinstall it using conda:

pip uninstall torch
conda install -c pytorch pytorch==2.4.0

Problems with Conda and Packages#

Incompatible Architecture

This is common when switching computers and transferring files through one drive and icloud. The solution is the same on MacOS, Linux and Windows:

conda install --upgrade --force-reinstall <package>
“Module not found… “ or “No Module Named”

If you have not previously installed the package the solution is to open your Terminal and write:

conda install <package>
“Module not found” - when you’ve installed the module

If you have installed the package before, you need to change your kernel. If you are using a Jupyter Notebook you have to go to the to right corner, where it says Python 3.XX.XX (this is the python version you are using). You need to click on it, after which a dropdown will come down. Here you need to click Select Another Kernel… ‣ Python Environments ‣ base (Python 3.11.XX). This will open the Python downloaded using our installation guides.

If you are using a normal Python script, go to the bottom right corner. Her it will only show the Python version, for example 3.12.XX 64-bit. You need to click this, after which a dropdown will come down. Here you can see your Python versions. If you want to use the version installed using our guides, select Python 3.11.XX (‘base’).

Sympy pretty print not functioning properly

When using sympy and the printing does not work after writing:

import sympy as*
init_printing()

Most of the cases can be solved by wrinting the following in stead:

import sympy as*
init_printing(use_latex='mathjax')
Multiple conda installations

If you have multiple installations of conda we highly recommend that you uninstall Anaconda using this link.

Problems with Visual Studio Code#

EPERM: Operation Not Permitted

This error occurs when your folder is in restricted mode, when you do not have access to the folder or when the folder is not trusted. To fix this:

  1. Check if the folder is in restricted mode. If it is, change the permissions.

  2. Check if you have access to the folder. If you do not, ask the owner for access.

  3. Check if the folder is trusted. If it is not, make sure that VS Code is allowed to access the folder.

“Module not found… “

This error occurs when you either have not installed the module or when the module is installed in a different environment. To fix this:

  1. Try to import the module in another environment (see here).

  2. If the module is not installed, install it using the command conda install module_name.

Missing “Run and debug” in Python files

This error occurs when you have not installed the Python extension. To fix this:

  1. Install the Python extension by clicking on the Extensions icon in the Activity Bar on the side of the window, searching for Python, and clicking on the Install button.

  2. If it still does not work, right-click on the three dots in the upper right corner next to where the run and debug button normally is. Then make sure that the run and debug have a checkmark.

Run and Debug