#Thonny import module code#
#Thonny import module mac#

If you're running your code in the Pico's REPL the file should be in the root folder of the micropython file system (this is not the file system exposed by the bootsel button). With pico and thonny it can depend on how thonny is configured. If you import foo the interpreter will look for a file called foo.py starting in the cwd. The interpreter must be able to find the required file(s) or the import will fail. Source and object code is the same thing.* Python is an interpreted language not a compiled one. You appear to misunderstanf some python fundamentals. I am certainly quite confused that in the stack trace above Thonny fails to import jedi which is directly importable from python3.Surely the source code for a project doesn't have to be on the target! but it's just weird enough to be confusing for learners I think, compared to any other instructions they would see for using pip, and hard to see all the output, compared to a routine console launch of pip install. It seems to work well from the Thonny shell like. I have even been speculating if I can use Thonny as a precursor to pip instead of installing python3.

#Thonny import module mac#

I am trying to minimise the number of steps involved, and the diversity across platforms by starting with pip3 and getting everything from there, such that the same instructions can be used for Linux, Mac and Windows. However, one of the reasons for looking into Thonny and Pip3 specifically is to benefit a project I am launching where users are expected to do python coding, and I am guiding them remotely. Thanks for the suggestion and clear guidance. Original comment by cefn (Bitbucket: cefn This is even though I get the following in a console. If jedi_utils.get_version_tuple() < (0, 9):įile '/home/cefn/.local/lib/python3.6/site-packages/thonny/jedi_utils.py', line 73, in get_version_tuple My_env = self._prepare_jedi()įile '/home/cefn/.local/lib/python3.6/site-packages/thonny/running.py', line 701, in _prepare_jediĮRROR: Failed loading plugin '_marker'įile '/home/cefn/.local/lib/python3.6/site-packages/thonny/workbench.py', line 245, in _load_plugins_from_pathįile '/home/cefn/.local/lib/python3.6/site-packages/thonny/plugins/locals_marker.py', line 141, in load_plugin

Self._proxy = backend_class(configuration_option)įile '/home/cefn/.local/lib/python3.6/site-packages/thonny/running.py', line 593, in _init_įile '/home/cefn/.local/lib/python3.6/site-packages/thonny/running.py', line 754, in _start_new_process ModuleNotFoundError: No module named 'jedi'ĮRROR: Failed loading plugin '_names'įile '/home/cefn/.local/lib/python3.6/site-packages/thonny/plugins/highlight_names.py', line 1, in įile '/home/cefn/.local/lib/python3.6/site-packages/thonny/workbench.py', line 287, in _init_runnerįile '/home/cefn/.local/lib/python3.6/site-packages/thonny/running.py', line 64, in startįile '/home/cefn/.local/lib/python3.6/site-packages/thonny/running.py', line 424, in reset_backend Return _bootstrap._gcd_import(name, package, level)įile '', line 955, in _find_and_load_unlockedįile '', line 219, in _call_with_frames_removedįile '/home/cefn/.local/lib/python3.6/site-packages/thonny/plugins/goto_definition.py', line 2, in INFO: Loading early plugins from ĮRROR: Failed loading plugin '_definition'įile '/home/cefn/.local/lib/python3.6/site-packages/thonny/workbench.py', line 243, in _load_plugins_from_pathįile '/usr/lib/python3.6/importlib/_init_.py', line 126, in import_module