Before running the user code, the app always runs import pyactr as actr. This is for the convenience of the user, but also so that we can catch errors/warnings with the initial import. (Which would not be a mistake in the user code.)
Currently, this is not communicated to the user at all, so users will import pyactr anyway. Importing a module twice does nothing, so this is not a major issue.
We could show the initial import statement as greyed-out code at the top of the code editor, so it's clear to the user they don't need to do this.
Before running the user code, the app always runs
import pyactr as actr. This is for the convenience of the user, but also so that we can catch errors/warnings with the initial import. (Which would not be a mistake in the user code.)Currently, this is not communicated to the user at all, so users will import pyactr anyway. Importing a module twice does nothing, so this is not a major issue.
We could show the initial import statement as greyed-out code at the top of the code editor, so it's clear to the user they don't need to do this.