Any Python file is a module, its name being the file’s base name without the .py extension. A package is a collection of Python modules: while a module is a single Python file, a package is a directory of Python modules containing an additional __init__.py file, to distinguish a package from a directory that just … Read more
RequireJS implements the AMD API (source). CommonJS is a way of defining modules with the help of an exports object, that defines the module contents. Simply put, a CommonJS implementation might work like this: // someModule.js exports.doSomething = function() { return “foo”; }; //otherModule.js var someModule = require(‘someModule’); // in the vein of node exports.doSomethingElse … Read more
You could use relative imports (python >= 2.5): from … import nib (What’s New in Python 2.5) PEP 328: Absolute and Relative Imports EDIT: added another dot ‘.’ to go up two packages
import a_module print(a_module.__file__) Will actually give you the path to the .pyc file that was loaded, at least on Mac OS X. So I guess you can do: import os path = os.path.abspath(a_module.__file__) You can also try: path = os.path.dirname(a_module.__file__) To get the module’s directory.
You can reload a module when it has already been imported by using importlib.reload(): from importlib import reload # Python 3.4+ import foo while True: # Do some things. if is_changed(foo): foo = reload(foo) In Python 2, reload was a builtin. In Python 3, it was moved to the imp module. In 3.4, imp was … Read more
help(‘modules’) in a Python shell/prompt.
It used to be a required part of a package (old, pre-3.3 “regular package”, not newer 3.3+ “namespace package”). Here’s the documentation. Python defines two types of packages, regular packages and namespace packages. Regular packages are traditional packages as they existed in Python 3.2 and earlier. A regular package is typically implemented as a directory … Read more