Import Expression Parser converts code like this:
urllib.parse!.quote('hello there')Into this equivalent code:
__import__('importlib').import_module('urllib.parse').quote('hello there')>>> import import_expression
>>> import_expression.eval('collections!.Counter("bccdddeeee")')
Counter({'e': 4, 'd': 3, 'c': 2, 'b': 1})The other public functions are exec, compile, parse, and find_imports.
See their docstrings for details.
By default, the filename for SyntaxErrors is <string>.
To change this, pass in a filename via the filename kwarg.
import_expression.eval/exec/compile should not be passed strings in a tight loop.
Doing so will recompile the string every time. Instead, you should pre-compile the string to a code object
and pass that to import_expression.eval / import_expression.exec.
For example, instead of this:
for line in sys.stdin:
print(import_expression.eval('foo!.bar(l)', dict(l=line))Prefer this:
code = import_expression.compile('foo!.bar(l)', mode='eval')
for line in sys.stdin:
print(import_expression.eval(code, dict(l=line)))Run import-expression for an import expression enabled REPL.
Run import-expression -a for a REPL that supports both import expressions and top level await (3.8+).
Combine these with -i to open a REPL after running the file specified on the command line. -ia allows top-level await.
See import-expression --help for more details.
Run import-expression <filename.py>.
- Due to the hell that is f-string parsing, and because
!is already an operator inside f-strings, import expressions inside f-strings will likely never be supported. - Due to python limitations, results of
import_expression.execwill have no effect on the caller's globals or locals without an explicitglobalsargument. - Unlike real operators, spaces before and after the import expression operator (such as
x ! .y) are not supported.
Copyright © io mintz <io@mintz.cc>. All Rights Reserved.
Licensed under the MIT License. See the LICENSE file for details.