pyj — Python with braces
English | 简体中文
Write Python like JavaScript: blocks in { }, statements separated by ; or newlines, and no significant whitespace. .pyj files are converted to standard Python transparently at import and run time, and errors point back to the original .pyj lines and columns.
def fib(n) { a, b = 0, 1; for _ in range(n) { a, b = b, a + b }; return a }
if n < 0 { print("negative") } else if n == 0 { print("zero") }
else { print("positive") }
Features
- Single file, zero dependencies: the whole tool is one
pyj.pythat uses only the standard library. - Transparent execution: once installed,
python app.pyjjust works, any program canimporta.pyjmodule, and.pyand.pyjfiles can be mixed freely. - Errors point to your source: tracebacks, syntax errors and
inspect.getsourceall show.pyjlines and columns. - Dicts and sets work as usual: pyj tells a block
{apart from a literal{. - Cross-platform: Python 3.10+, tested in CI on Linux, macOS and Windows.
Installation
With pip (recommended)
pip install pybrace
After installing, every Python process in that environment understands .pyj files. pip uninstall pybrace removes it completely. The package is named pybrace on PyPI, but the module and the command are both pyj.
python app.pyj arg1 arg2 # run directly
python -c "import mymod" # import any .pyj module; packages can use __init__.pyj
pyj build app.pyj # convert to app.py
.pyjand.pymodules can import each other. If bothfoo.pyandfoo.pyjexist,foo.pyjwins.- Compiled code is cached in
__pycache__/<module>.pyj.cpython-XY.pyc. The cache is invalidated when the source file or pyj itself changes. - How
python app.pyjworks: at startup Python runspyj_autoload.pthfrom site-packages. When it sees that the script is a.pyjfile, it replaces the process withpython -m pyj app.pyj(on Windows it starts a child process instead). Interpreter flags are preserved.
Single file, no pip
Put pyj.py anywhere and run:
python pyj.py install # writes pyj_autoload.pth; same effect as pip install (inside a venv, only that venv)
python pyj.py uninstall # undo
Without installing anything
python pyj.py run app.pyj [args...] # or: python pyj.py app.pyj
python pyj.py build app.pyj # writes app.py
python pyj.py build app.pyj -o - # prints to stdout
From Python code:
import pyj
pyj.install_import_hook() # .pyj modules become importable
print(pyj.transpile("if x { y() }"))
code = pyj.compile_pyj(src, "file.pyj") # code object with positions mapped to the .pyj source
Error locations
Runtime exceptions, syntax errors, inspect.getsource and linecache all point to the exact line and column in the .pyj source. This holds even when several statements share a line or one expression spans several lines:
File "util.pyj", line 3, in divide
return a /
~~^
b }
~
ZeroDivisionError: division by zero
How it works: while converting, pyj records where each token came from in the source. It parses the generated code with ast.parse, rewrites every AST node's position back to the source position, and then compiles.
Syntax
| Rule | Example |
|---|---|
Blocks use { }; indentation is free-form |
while x { x -= 1 } |
| The colon is optional | def f(): { ... } is the same as def f() { ... } |
Statements are separated by ; |
a = 1; b = 2 |
| A newline ends a statement when the statement is clearly complete | One statement per line needs no ; |
| Newlines inside brackets, or after a trailing operator or comma, are ignored | total = 1 +⏎2 |
A line starting with . , and or etc. continues the previous line |
s = text⏎.strip() |
else if is shorthand for elif |
} else if x { |
Empty blocks get pass automatically |
class E {} |
| Dicts and sets are written as usual | if k in {1, 2} { d = {} } |
How does pyj tell blocks from dicts? A { opens a block only when it ends the header of an if/for/while/def/class/try/with/match/case… statement, that is, when it follows a name, number, string, closing bracket, :, or else/try/finally/except. In Python an expression followed by { is never valid, so this is unambiguous.
Caveats
- A line starting with
(,[,-or*does not continue the previous line. This avoids the JavaScript pitfall wherea⏎(b)becomes a function call. To continue a line, put the operator at the end of the line or wrap the expression in parentheses. - In a compound statement header written as
if x: {...}, the{always opens a block. To put a dict expression after a one-lineif, wrap it in a normal{ }block. - Comments are preserved. A comment in the middle of an expression is moved to the end of that statement's line.
Development
python -m unittest discover -s tests -v
License
Metadata
Release files for pybrace 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pybrace-0.1.1.tar.gz | 17.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pybrace-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.8 kB
Release files / pybrace-0.1.1.tar.gz
| Download URL | pybrace-0.1.1.tar.gz |
|---|---|
| Size | 17.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0df0c97464c9025626559ff22b74ee1fe6c6d7442d7cc83e9f4d559eb890f28f
|
|
BLAKE2b-256 checksum How to use checksums |
b8129dc5ee87e490a48573a53f681b8ebe291edb73bed6597b2c7be83ea0454d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.
Transparency logRelease files / pybrace-0.1.1-py3-none-any.whl
| Download URL | pybrace-0.1.1-py3-none-any.whl |
|---|---|
| Size | 13.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4f6d7e43c829ad5e8aef3d5e5d69bfcb4c4384857630f3fb77a1b386e6a47696
|
|
BLAKE2b-256 checksum How to use checksums |
e38d00117ea89611ca619cd208fcd48c9feb68435030a6909b69e62978ea9b02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.
Transparency log