This page says how to install Bogolang on Windows and on Linux, on a PC with or without internet, how to add another Python engine, and how to remove Bogolang. It also says what the installation carries and what it takes from the PC.
The installers are published on the releases page of the project, with a file of their SHA-256 sums. Compare the sum of the file you downloaded with the published one before you run it.
| Windows | Linux | |
|---|---|---|
| The file | bogolang-VERSION-windows-x64.exe |
bogolang-VERSION-linux-x64.run |
| The machine | 64-bit x86 | 64-bit x86, a Linux built on the GNU C library (Ubuntu, Debian, Red Hat and the like) |
| Administrator right | Not needed | Not needed, but for one optional setting (below) |
| Internet | Not needed | Not needed |
| Installed in | %LOCALAPPDATA%\Bogolang |
~/.local/share/bogolang |
The command bogo |
Its folder is added to the PATH of the user | A link in ~/.local/bin |
| Removed with | "Apps" in the settings of Windows | bogo uninstall |
Bogolang installs for the current user only. Version 0.1.0 is a first version for trial.
Windows
- Download
bogolang-0.1.0-windows-x64.exe. - Run it. The file is not signed, so Windows shows an "unknown publisher" warning. Check the SHA-256 sum first if you have not.
- The one choice it offers is a "Bogolang Shell" icon on the desktop. The box is off by default.
- Open a new terminal, so that it reads the new PATH, and type:
bogo version
Bogolang 0.1.0, engine Python 3.15
The installer adds two entries to the Start menu, under "Bogolang":
| Entry | What it opens |
|---|---|
| Bogolang Shell | A terminal window that runs bogo shell, in your Documents folder |
| Bogolang Terminal | A terminal window in your Documents folder, with bogo ready |
The installer file is about 51 MB. The installed folder is about 264 MB. For an installation
with no window at all, the installer takes the usual Inno Setup option /VERYSILENT.
bogo upgrade fetches the newest version, checks its sum and starts its installer:
tools.md says how. With Python and pip already on a PC, pip install bogolang
gives a command bogolang-install that does the same for a first installation.
Installing a new version over an older one replaces it. The files of the older one are removed first; nothing outside the folder of Bogolang is touched.
Linux
- Download
bogolang-0.1.0-linux-x64.run. - Run it as your own user, not as root:
sh bogolang-0.1.0-linux-x64.run
The installer needs two tools of the system to unpack itself: tar and xz. A usual Linux
has both. A bare system, such as a container image or a minimal install of the Red Hat
family, may lack them. The installer then stops with xz: command not found or
tar: command not found and installs nothing. Add them first, as an administrator:
| System | Command |
|---|---|
| Red Hat, Rocky, Alma, Fedora | dnf install tar xz |
| Debian, Ubuntu | apt install tar xz-utils |
These two are the only tools of the system the installer uses. Once installed, Bogolang uses none.
The installer first checks that its engine starts on this machine. If it does not, it says so and stops:
Bogolang cannot run on this machine: its engine does not start here.
It needs a 64-bit x86 Linux built on the GNU C library, such as Ubuntu, Debian or Red Hat.
It then places Bogolang in ~/.local/share/bogolang, links the command in ~/.local/bin,
and adds "Bogolang Shell" to the applications menu (on a machine with no desktop this
changes nothing). An older Bogolang in the same place is replaced. It writes nothing outside
your home folder, but for the ping setting below. It ends with Type: bogo --help and
To remove Bogolang later: bogo uninstall.
If ~/.local/bin is not on your PATH, it says so and gives the line to add to
~/.profile. It changes no shell setting itself:
export PATH="$HOME/.local/bin:$PATH"
The installer file is about 69 MB. The installed folder is about 444 MB.
The one question: the ping setting
Bogolang sends its own ping packets, with no system tool. On Linux it uses the ICMP socket
that the system offers to ordinary users. A setting of the system, net.ipv4.ping_group_range,
can keep that socket closed. Most current systems open it; some do not.
The installer tries the socket. If it opens, nothing is asked. If not, and a person is at the keyboard, it asks:
Bogolang's own ping needs one setting of this system, which is closed here.
Opening it needs the administrator password, once. Without it, ping() uses the ping command of the system.
Open it now? [y/N]
On yes, it asks for the administrator password through sudo, once. It then writes one file,
/etc/sysctl.d/60-bogolang-ping.conf, with the line
net.ipv4.ping_group_range = 0 2147483647, and applies it at once. Where the system refuses
that value, as some containers do, it writes 0 65535 instead. It tries the socket again and
says the result. The setting then holds after every restart.
What this changes: ordinary users of that machine may open the ICMP socket, the system's own way to allow ping without root. It gives Bogolang no other right. It opens ping to the other programs of that machine too, as it already is on most systems. It is the one file Bogolang writes outside your home folder.
On no, with no keyboard, or if sudo fails, nothing is written. ping(), ping_all() and
scan() then use the ping command of the system, and say so once per run. The inputs
size, interval, ttl, source, dont_fragment and dscp have no effect that way.
trace() then sends UDP probes, which need no setting; a target that answers a ping but
stays silent to a UDP probe is then not shown as the last hop. To open the setting later, an
administrator runs the line the installer prints:
sudo sh -c "echo 'net.ipv4.ping_group_range = 0 2147483647' > /etc/sysctl.d/60-bogolang-ping.conf && sysctl -p /etc/sysctl.d/60-bogolang-ping.conf"
A PC with no internet
The installers need no internet. Copy the file to the PC and run it.
- A new project downloads nothing. Its environment sees the packages that Bogolang carries, and holds only what the project adds.
bogo add NAME --from FOLDERandbogo sync --from FOLDERinstall packages from package files brought in a folder.bogo engine install VERSION --from FILEadds an engine from a file brought by hand.bogo packneeds no internet.
Another Python engine: bogo engine install
Bogolang runs on its own Python 3.15 engine, and a new project uses it. A project may choose another engine.
bogo engine list
bogo engine install 3.14
bogo engine use 3.14
bogo engine install VERSIONreads the list of engines of the project python-build-standalone, the same source as the engine of the installer. It downloads the file for this system and compares its SHA-256 sum with the published one before anything is unpacked. With no published sum, nothing is downloaded.bogo engine install VERSION --from FILEcontacts nothing. Bring the filecpython-VERSION...-install_only_stripped.tar.gzfor your system from that project. The command prints the SHA-256 sum of the file, for you to compare with the one published where it came from.- Before an engine is accepted, it is started once and asked its version. A file that holds another version than the one asked is refused, and nothing is placed.
- Engines go to
~/.bogolang/engines. Only 64-bit x86 on Windows and on a Linux built on the GNU C library. bogo engine use VERSION, typed in a project, writes the engine inbogo.toml. The environment of the project is made again at its next run.
A project on another engine needs its own copies of the packages of the built-in commands,
since compiled packages fit one engine only. They come from the internet, or from
bogo sync --from FOLDER. Without them the device commands do not work in that project, and
a warning says so.
Removal
Windows. Open the settings of Windows, "Apps", and remove "Bogolang 0.1.0". This removes
the folder, the PATH entry, the Start menu entries and the desktop icon. bogo uninstall on
Windows says the same.
Linux.
bogo uninstall
It asks first, naming the folder in full:
Remove Bogolang from /home/USER/.local/share/bogolang?
Projects, stored logins and the folder ~/.bogolang are left alone. [y/N]
On yes it removes the folder, the link in ~/.local/bin (only if it points to this
Bogolang), the menu entry and the icons. bogo uninstall --yes does not ask.
If the installer wrote the ping setting file, bogo uninstall then says where it is and asks
whether to remove it too, with the administrator password again. The file is what makes the
setting last: once it is removed, the setting stays open until the next restart, and is closed
after it. With --yes, or with no keyboard, it does not ask and prints the line to type:
sudo rm /etc/sysctl.d/60-bogolang-ping.conf
On both systems removal leaves alone your projects, the logins stored in the protected store
of the system, and the folder .bogolang in your home folder (the cache of checks and the
added engines). Delete that folder by hand if you want it gone.
What the installation carries
| Folder | What it holds |
|---|---|
bin |
The command bogo. On Windows a small .exe, on Linux a short shell script |
engine/3.15 |
A private Python 3.15 engine, from python-build-standalone, unchanged |
| inside the engine | Bogolang, the type checker (mypy), the formatter (Black), the packer (PyInstaller), and the packages of the built-in commands (Netmiko, paramiko, pysnmp, keyring, openpyxl, python-docx, matplotlib and their own needs), at versions tested together |
tools |
Linux only: objdump and objcopy of GNU binutils, for bogo pack |
examples |
The thirteen programs of ../examples, with their saved answers |
docs |
These pages |
LICENSES |
The licence of every part carried, and a list of them |
The source of the carried binutils is published beside the Linux installer, as its licence asks.
Bogolang runs on its own resources
Many PCs have a Python already. Bogolang does not use it and does not disturb it.
- The command
bogostarts the engine by its full path. It never looks forpythonon the PATH, and never uses thepylauncher of Windows. - The engine always runs in Python's isolated mode, and so does every process Bogolang starts
(the check, the tests, the shell, pip). It ignores
PYTHONPATH,PYTHONHOME,PYTHONSTARTUPand the packages installed for a Python of the user. - It puts one name on the PATH:
bogo. Nopython, nopip. It writes no Python entry in the Windows registry and takes no file type:.pyfiles open as before. - A project environment is made from the engine of Bogolang and sees its packages only.
What it still takes from the PC, said plainly:
| Taken from the PC | Why |
|---|---|
| The system itself: the libraries of Windows, the GNU C library on Linux | Every program does |
| The protected store of the system | Logins and tokens are kept there, not in files |
| The network settings: proxy, DNS, certificates | To reach devices and to add packages |
| The pip settings of the user, if any | So a company package index or proxy keeps working for bogo add |
The ping command of the system, on a Linux where the ping setting stays closed |
See above |
This was proven during each build of the installers and on a real installation, on a PC that has other Pythons installed. A PC with no Python at all was not tried (not-proven.md).
Without the installer
Bogolang can also run from its source, installed with pip into a Python 3.15 of your own. It
works the same way, but it runs on that Python: the isolation above does not apply, and on
Linux bogo pack takes objdump and objcopy from the system (package binutils).