This release is a pre-release and may not be stable for production use.
The pillar of The Sirio Network
TSN Abstracter (also called TSNA) is a monolithic Python Module containing commonly used functions to avoid rewriting them for every project.
TSNA can be used to make fully featured Terminal Applications or CLI Based tools with some ease. It is however crucial to mention that TSNA lacks any formal documentation, only DocStrings within the Python Files are the unique type of documentation available for TSNA.
TSN Abstracter is currently used to power numerous tools and applications built by The Sirio Network such as:
Installation / Usage
TSNA has been historically been without a proper Python Package, this however finally changes now.
You should simply be able to run pip install TSN-Abstracter nowadays.
TSNA however on Adellian still installs TSNA the old way by cloning the repository then adding the folder path to your PYTHONPATH.
All projects from The Sirio Network thus installs TSNA this way and thus are only tested as such.
In the case of Adellian, with an installation at /System/Library/TSN_Abstracter, the .bashrc contains the following line: export PYTHONPATH=/System/Library/TSN_Abstracter:$.
You can do something similar if you wish to install TSN Abstracter the old way.
All that's left to do after installation is to simply include at the very top of your Python script from TSN_Abstracter import *; and then get to roll with it.
We recommend the following template file Python File to start your TSNA fueled programs:
# [Program] (c) [Author] (Date) - [License]
from TSN_Abstracter import *;
Debug_Mode: bool = Root_CFG["Debug"];
if (__name__ != "__main__"): TSN_Abstracter.Import_Unsupported(); # Remove this if your script can be imported as a Python Module
else:
TSN_Abstracter.App_Init(True);
Config.Logger.Print_Level = 15 if (Debug_Mode) else 20;
Config.Logger.File = True;
# Do whatever your program does here
...
TSNA automatically attempts to read data from App.tsna, this file contains basic information about your application:
{
"Name": "Tachibana",
"Description": "Tachibana is a (work in progress) TSNA-Based rewrite of Adellian's SSHMan Application.",
"Author": ["Ascellayn", "The Sirio Network"],
"Contributors": [],
"License": "TSN License 2.1 - Base",
"License_Year": "2026",
"Codename": "TSN_Tachibana",
"Branch": "Azure",
"Version": [1,0,0],
"Version_Prefix": "",
"Version_Suffix": "_dev",
"TSNA": [6,0,0], # Minimum required TSNA Version for the Application to run,
"Public": {}, # You can put anything in there, used for application-specific options.
"Private": {} # Application's private data to be only used internally. This is not meant to be present in the App.tsna file.
}
TSN Abstracter is obviously developer oriented, it is your job to look at TSNA and find functions that are deemed useful to you.
Dependencies
- The "LZMA" Python Module (should be shipped with your OS's Libraries)
- If you import the "Cryptography" TSNA Module":
- python3-cryptography
- If you import the "TUI" TSNA Module":
- python3-curses
Random facts about TSNA
TSN Abstracter was created in early 2025 after things started getting hectic when it came to creating stuff such as (at the time) Kosaka and TSN Trinity. I would constantly have this TSNDB_Dependencies.py or SN_PyDepends file that I'd have to manually synchronize across all those projects. At some point I decided enough was enough and thus TSN Abstracter was born.
If we have to take in when TSNA was truly created then it was created during Kosaka's Pre-Ceres Lifecycle, which was in the middle of 2024.
TSNA was created so early it does not follow TSN's naming conventions, thus, a Blue Archive character or thing was never attributed as its codename / name.
New coding style conventions or things such as the TSN Commit Guideline had their start in TSNA.
TSN Abstracter (TSNA) © Ascellayn / The Sirio Network (2025-2026) - TSN License 2.1 - Base
Release files for TSN-Abstracter 7.0.0a4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| tsn_abstracter-7.0.0a4.tar.gz | 47.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tsn_abstracter-7.0.0a4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 102.0 kB
Release files / tsn_abstracter-7.0.0a4.tar.gz
| Download URL | tsn_abstracter-7.0.0a4.tar.gz |
|---|---|
| Size | 47.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa578826eec867410a4761c2ea8bc4af789207c68e9fd43423e13829a28124ac
|
|
BLAKE2b-256 checksum How to use checksums |
2ac05ba314ceb4c4262e0859930a48535dbf5702bb76bd902964dc416b02e360
|
| 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 Sep 16, 2026.
Transparency logRelease files / tsn_abstracter-7.0.0a4-py3-none-any.whl
| Download URL | tsn_abstracter-7.0.0a4-py3-none-any.whl |
|---|---|
| Size | 54.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e6640249228b8fcf27721f8f830360720c0da0a74cb54944f3879c67dcc71afc
|
|
BLAKE2b-256 checksum How to use checksums |
4aaf00e59186c762b2d7d3d29eebac172f2698daf12ab4775626905733ff04be
|
| 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 Sep 16, 2026.
Transparency log