Interactive BrainFuck
An interactive BrainFuck interpreter written in Bython. Why not?
To install from source, you must first build the Bython source into a Python package:
$ make build
Then, you move to the python folder, and run the setup script:
$ cd python
$ sudo -H pip3 install .
After installation, you run an interactive session with the ibf command:
$ ibf
Interactive BrainFuck - ibf v0.1
ibf is licensed under the permissive MIT license. Full license and
copyright information is available at the project's GitHub repository.
[Input] +[------->++<]>-.------------.--[--->+<]>--.+.+++[->+++<]>.+++++++++++++.[-->+++++<]>+++.[-->+++++++<]>.++.---.------------.-[--->+<]>----.+++[->+++<]>++.--[--->+<]>--.+.-----------.+++++.-------------.--[--->+<]>-.-----.+++.>++++++++++.
master procrastinator
Everything you input is interpreted as BrainFuck code, except for the following reserved keywords:
| Command | Description |
|---|---|
| tape | Prints the current status of the tape (data cells), with the current cell in bold |
| pos | Prints the current position on the tape |
| quit | Quits the session |
| run | Run code from a file |
You can also run prewritten BrainFuck code, either as a standalone program, or in an interactive session:
$ ibf test.bf
Hello World!
$ ibf
Interactive BrainFuck - ibf v0.1
ibf is licensed under the permissive MIT license. Full license and
copyright information is available at the project's GitHub repository.
[Input] run test.bf
Hello World!
The run command always runs programs inline, ie the code is run on the
current tape and with the current tape position as starting position. Thus,
after running a program you can inspect the final state of the tape:
[Input] tape
0 1 2 3 4 5 6 7 8
0 0 72 100 87 33 10 0 0
For more help, type ibf -h or view the manual page by running man ibf.
Metadata
Release files for ibf 0.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 | Provenance | Actions |
|---|---|---|---|---|
| ibf-0.1.tar.gz | 6.4 kB | Without provenance | Details for ibf-0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ibf-0.1-py3-none-any.whl | Python 3 | none | any | Details for ibf-0.1-py3-none-any.whl |
Total release size: 14.5 kB
Release files / ibf-0.1.tar.gz
| Download URL | ibf-0.1.tar.gz |
|---|---|
| Size | 6.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
442ab9eaa329da3d8da656c2c6337c6a43278b632d7c51bbfd13ac3b060df67b
|
|
BLAKE2b-256 checksum How to use checksums |
9bdb7d9494b51e449ee9e3b491312a87e59ef8e6cebb0c1905fe52c97e4773bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/39.1.0 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.5.2
|
Release files / ibf-0.1-py3-none-any.whl
| Download URL | ibf-0.1-py3-none-any.whl |
|---|---|
| Size | 8.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f6caa62cd0e2a9a4d7ef396b4732ad179a51a67217b096968910e7342f37e403
|
|
BLAKE2b-256 checksum How to use checksums |
641d9f97d094f8006b58074aa1432c7150a523d396f0ade270d63ab18364b898
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/39.1.0 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.5.2
|
Security for ibf 0.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.