SATIF Core
Core abstractions and types for the SATIF toolkit.
Table of Contents
Overview
The satif_core package serves as the foundational library for the SATIF ecosystem. It provides a collection of essential base classes, abstract interfaces, custom data types, and common exceptions that are utilized by other SATIF components to ensure consistency and facilitate interoperability within the system.
This package does not contain concrete implementations or executable logic for end-users. Instead, it defines the contracts and building blocks upon which the rest of the SATIF system is built.
Intended Audience & Usage
satif_core is intended for internal development within the SATIF project. It is not designed for direct usage by end-users or applications seeking to perform data transformations.
Other SATIF libraries (e.g., satif-sdk) will use the abstractions and types defined in satif_core to build their respective components.
Contributing
Contributions to satif_core are welcome, especially those that refine existing abstractions or propose new fundamental components beneficial to the SATIF ecosystem. As this is a core library, changes will be reviewed carefully for their impact on the overall architecture.
Please follow the general contribution guidelines for the SATIF project:
- Fork the repository on GitHub.
- Clone your fork locally.
- Create a new branch for your feature or bug fix.
- Set up the development environment (refer to the main SATIF project or relevant sub-project for build/dev environment details).
- Make your changes. Ensure your code adheres to PEP 8 and includes comprehensive docstrings and type hints.
- Add or update tests for your changes.
- Run linters, type checkers, and tests to ensure code quality and correctness.
- Commit your changes with a clear and descriptive commit message.
- Push your changes to your fork.
- Submit a Pull Request (PR) to the
mainbranch of the originalsyncpulse-solutions/satifrepository.
License
This project is licensed under the MIT License - see the LICENSE file in the SATIF project root for details.
Release files for satif-core 0.3.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 | |
|---|---|---|---|
| satif_core-0.3.1.tar.gz | 11.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| satif_core-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.8 kB
Release files / satif_core-0.3.1.tar.gz
| Download URL | satif_core-0.3.1.tar.gz |
|---|---|
| Size | 11.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cff324f2da856830df52164ca81977a6d7f69e8b0882802ea3c1391ff8bca818
|
|
BLAKE2b-256 checksum How to use checksums |
cbf36c0cdaa4d8ef3a7a7640a69a8f733b90e4ca80a1ca0e673ffa61029ce042
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 May 20, 2025.
Transparency logRelease files / satif_core-0.3.1-py3-none-any.whl
| Download URL | satif_core-0.3.1-py3-none-any.whl |
|---|---|
| Size | 16.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
82dd85ecf66437290cbdea7e7460cbe89f88c71a405b2373b6bcfee859bc3d54
|
|
BLAKE2b-256 checksum How to use checksums |
10ed5a21eb59f152ca8eba2d26967d099422fb50878965e8c9cfd6ece08a62e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 May 20, 2025.
Transparency log