NAME
nixt - NIXT
SYNOPSIS
DESCRIPTION
nixt has all you need to program a unix cli program, such as disk perisistence for configuration files, event handler to handle the client/server connection, deferred exception handling to not crash on an error, etc.
nixt contains all the python3 code to program objects in a functional way. It provides a base Object class that has only dunder methods, all methods are factored out into functions with the objects as the first argument. It is called Object Programming (OP), OOP without the oriented.
nixt allows for easy json save//load to/from disk of objects. It provides an “clean namespace” Object class that only has dunder methods, so the namespace is not cluttered with method names. This makes storing and reading to/from json possible.
nixt is a demo bot, it can connect to IRC, fetch and display RSS feeds, take todo notes, keep a shopping list and log text. You can also copy/paste the service file and run it under systemd for 24/7 presence in a IRC channel.
nixt is Public Domain.
INSTALL
installation is done with pipx
if you run nixt locally from source you might need to add your current directory to sys.path
USAGE
use nixt to control the program, default it does nothing
see list of commands
start daemon
start service
COMMANDS
here is a list of available commands
CONFIGURATION
irc
sasl
rss
opml
PROGRAMMING
nixt runs it’s modules in the package, to add your own command edit a file in nixt/modules/hello.py and add the following for hello world
def hello(event):
event.reply("hello world !!")
save this and run
program can execute the hello command now.
commands run in their own thread, errors are deferred to not have loops blocking/breaking on exception and can contain your own written python3 code, see the nixt/modules directory for examples.
FILES
AUTHOR
COPYRIGHT
Metadata
Release files for nixt 160
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 | |
|---|---|---|---|---|
| nixt-160.tar.gz | 32.9 kB | Without provenance | Details |
Release files / nixt-160.tar.gz
| Download URL | nixt-160.tar.gz |
|---|---|
| Size | 32.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
743d2fe18dbbce9ed8fa48d98da90be2f7cb6917d52651d9f26506bbc6d42fe8
|
|
BLAKE2b-256 checksum How to use checksums |
4d51806d15b02d8d9d20875e55a8482d053119630c321adb4261a8d7e19ffb72
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for nixt 160
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.