RHDZMOTA Package
Rodrigo H. Mota's personal python package that contains general tooling for facilitating the development of software engineering, data engineering, and machine learning projects.
Aren't toolbox packages usually heavy? One main concern of designing toolbox packages shared across projects is that the dependency set often becomes too heavy. This is specially true for data-related projects (e.g., installing pandas, request, tensorflow, sklearn, etc). To solve this issue, the rhdzmota package offers "package extensions" that can be installed by specifying their corresponding tags. This allows us to "split" the dependency set and functionality in sub-python packages; resulting in a lightweight and modular toolbox!
How can I install a package extension? You just need to specify their corresponing "extras-require" tag. Example:
$ pip install 'rhdzmota[ext.hello_world]'
All the package extensions tag will follow the pattern: ext.*
Are there any import patterns to consider? Yes, both the core package and the extensions share a common namespace: rhdzmota. The core package contains their modules directly at the first level (e.g., rhdzmota.*) and the extensions share an inner namespace (i.e., rhdzmota.ext) resulting in the following pattern: rhdzmota.ext.{{ext-slug}}).
The following example imports the Env enum from the settings module in the core package and the hello function from the hello_world extension.
from rhdzmota.settings import Env
from rhdzmota.ext.hello_world.functions import hello
...
Metadata
Release files for rhdzmota 4.0.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 | Provenance | Actions |
|---|---|---|---|---|
| rhdzmota-4.0.1.tar.gz | 25.0 kB | Without provenance | Details for rhdzmota-4.0.1.tar.gz |
Release files / rhdzmota-4.0.1.tar.gz
| Download URL | rhdzmota-4.0.1.tar.gz |
|---|---|
| Size | 25.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ee9fb93ea2d6ea7cf89700fb0c0d0a7959b083ac0951d858bd69e91df386323c
|
|
BLAKE2b-256 checksum How to use checksums |
a3773e5e5f7b94e6f0a39b6af2eea20468b47a7fe019bc301900ccbbfd09d425
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.10.12
|
Security for rhdzmota 4.0.1
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.