If, like me, you are running your django in a virtualenv, and getting this error, look at your manage.py. The first line should define the python executable used to run the script. This should be the path to your virtualenv’s python, but it is something wrong like /usr/bin/python, which is not the same path and … Read more
You can import the variables from the file: vardata.py verb_list = [x, y, z] other_list = [1, 2, 3] something_else = False mainfile.py from vardata import verb_list, other_list import random print random.choice(verb_list) you can also do: from vardata import * to import everything from that file. Be careful with this though. You don’t want to … Read more
With Python older than 2.7/3.1, that’s pretty much how you do it. For newer versions, see importlib.import_module for Python 2 and Python 3. You can use exec if you want to as well. Or using __import__ you can import a list of modules by doing this: >>> moduleNames = [‘sys’, ‘os’, ‘re’, ‘unittest’] >>> moduleNames … Read more
If you do import foo (inside bar.py) and import bar (inside foo.py), it will work fine. By the time anything actually runs, both modules will be fully loaded and will have references to each other. The problem is when instead you do from foo import abc (inside bar.py) and from bar import xyz (inside foo.py). … Read more
For Python 3.5+ use (docs): import importlib.util import sys spec = importlib.util.spec_from_file_location(“module.name”, “/path/to/file.py”) foo = importlib.util.module_from_spec(spec) sys.modules[“module.name”] = foo spec.loader.exec_module(foo) foo.MyClass() For Python 3.3 and 3.4 use: from importlib.machinery import SourceFileLoader foo = SourceFileLoader(“module.name”, “/path/to/file.py”).load_module() foo.MyClass() (Although this has been deprecated in Python 3.4.) For Python 2 use: import imp foo = imp.load_source(‘module.name’, ‘/path/to/file.py’) foo.MyClass() … Read more
I set the PYTHONPATH to ‘.’ and that solved it for me. export PYTHONPATH=’.’ For a one-liner you could as easily do: PYTHONPATH=’.’ your_python_script These commands are expected to be run in a terminal
This error occurs because, the path to the file app_one is not in the current path, and you have to add it to the path using sys.path.append Try : import sys sys.path.append(‘./app_one’) from views import show show()
This typically occurs when multiple versions of python are installed with different paths. You can check to see if you have multiple installations by opening up the IDLE terminal and using import sys sys.version sys.path These commands will print the system PATH and version of the current instance of python. Use this in both IDLE … Read more
PEP 8 authoritatively states: Imports are always put at the top of the file, just after any module comments and docstrings, and before module globals and constants. PEP 8 should be the basis of any “in-house” style guide, since it summarizes what the core Python team has found to be the most effective style, overall … Read more
I believe by “in the middle of your program” you are talking about an import inside a function definition: def f(): from module import * # not allowed This is not allowed because it would make optimizing the body of the function too hard. The Python implementation wants to know all of the names of … Read more