Certainly! Here's a suggested structure for your oliseh_efris_tools library along with a README file explaining its usage:
oliseh_efris_tools Library Structure
oliseh_efris_tools/
│
├── client.py
├── data.py
├── globaldata.py
├── headers.py
├── returnstateinfo.py
├── __init__.py
└── README.md
README.md
# oliseh_efris_tools
`oliseh_efris_tools` is a Python library that provides tools for interacting with the OLISEH eFRIS (Electronic Fiscal Receipting and Invoicing System) API. It offers functionalities for managing global data, request data, headers, and return state information.
## Installation
You can install `oliseh_efris_tools` via pip:
```bash
pip install oliseh-efris-tools
Usage
Client
The Client class serves as the main interface for interacting with the OLISEH eFRIS API. It provides methods for setting global data, request data, headers, and handling return state information.
Example usage:
from oliseh_efris_tools import Client
# Initialize Client with the URL of the OLISEH eFRIS API
client = Client("https://efris.ura.go.ug/")
# Set global data
client.set_global_key("appId", "AP01")
client.set_global_key("version", "1.1.20191201")
# Add more global data as needed...
# Set request data
client.Data.set_content("encrypted content")
client.Data.set_signature("JKQWJK34K32JJEK2JQWJ5678")
client.Data.set_data_description("0", "1", "0")
# Add more request data as needed...
# Set headers
client.Headers.set_header("User-Agent", "MyApp/1.0")
# Add more headers as needed...
# Send request
client.send_request()
Additional Components
- GlobalData: Manages global information.
- Data: Manages request data.
- Headers: Manages HTTP headers.
- ReturnStateInfo: Manages return state information.
Contributing
Contributions are welcome! If you have suggestions or find any issues, feel free to open an issue or submit a pull request on GitHub.
License
This project is licensed under the MIT License. See the LICENSE file for details.
By time of writing this
the URA endpoint is `"https://efris.ura.go.ug/"`
Metadata
Release files for oliseh-efris-tools 0.1.0
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 |
|---|---|---|---|---|
| oliseh-efris-tools-0.1.0.tar.gz | 2.2 kB | Without provenance | Details for oliseh-efris-tools-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| oliseh_efris_tools-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for oliseh_efris_tools-0.1.0-py3-none-any.whl |
Total release size: 4.5 kB
Release files / oliseh-efris-tools-0.1.0.tar.gz
| Download URL | oliseh-efris-tools-0.1.0.tar.gz |
|---|---|
| Size | 2.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
04c8beba523efcc8f09e757242c5541de560576a53b8b9c71b276df9f573a2ce
|
|
BLAKE2b-256 checksum How to use checksums |
357a5b5a61fc10029b9135afddf50a1fc31fd0f1bbc4ca04c610c0f1ce227461
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.10.0
|
Release files / oliseh_efris_tools-0.1.0-py3-none-any.whl
| Download URL | oliseh_efris_tools-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
686900d206774acaf6ba45f69a8764f616e9d8a2f9ca389463fa254cff4aeb69
|
|
BLAKE2b-256 checksum How to use checksums |
775b70f135f417d4ef8ab8649cc7cb3b729458000c0b0ad551f0a6e95e06abf7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.10.0
|
Security for oliseh-efris-tools 0.1.0
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.