uai
This package allows to quickly initialise new Python package using bleeding edge tools like linters, just run:
pip install uaiuai <your-package-name>
Now you are able to:
cd <your-package-name>make check # To run tests and lintersmake publish # To publish your new package to PyPi.org to make it accessable to everyone
This is also a boilerplate for a new python package, so you can create a new package this way as well:
git clone git@github.com:albertas/uai.git <your-package-name>cd <your-package-name>make init <your-package-name>- to start your modern package.
Development
Commonly used commands for package development:
make check- run unit tests and linters.make fix- format code and fix detected fixable issues.make publish- publishes current package version to pypi.org.make compile- bump and freeze dependency versions in requirements*.txt filesmake sync- upgrade installed dependencies in Virtual Environment (executed aftermake compile)
Toolset
This package uses these cutting edge tools:
- ruff - for linting and code formatting
- mypy - for type checking
- pip-audit - for known vulnerability detection in dependencies
- deadcode - for unused code detection
- pytest - for collecting and running unit tests
- coverage - for code coverage by unit tests
- hatch - for publishing package to pypi.org
- uv - for Python virtual environment and dependency management
- pyproject.toml - configuration file for all tools
- Makefile - aliases for commonly used command line commands
Feature requests:
- Newly installed package could have virtualenv initialised.
- Check if
gitis available before trying to initialise the repository. - remove init Makefile alias and cli.py command python files.
- make a cli command: this package should be installable. Ideally this flow should work:
pip install uaiuai mynewpackagecd mynewpackage&&make check&&make publish
- Add pre-commit hooks with all the tools enabled.
- codspeed.io could be considered for Continuous integration pipeline
Metadata
Release files for uai 0.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 |
|---|---|---|---|---|
| uai-0.0.1.tar.gz | 4.4 kB | Without provenance | Details for uai-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| uai-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for uai-0.0.1-py3-none-any.whl |
Total release size: 7.7 kB
Release files / uai-0.0.1.tar.gz
| Download URL | uai-0.0.1.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0323cf2a09a04e0ef875e90f2462aeeff46107cbbbdf5f0223d856cbaa4bd5a8
|
|
BLAKE2b-256 checksum How to use checksums |
3cb92019e52efd894f807a813f8a23bb064d994c4d8b42c0fa9862127ed067a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.27.2
|
Release files / uai-0.0.1-py3-none-any.whl
| Download URL | uai-0.0.1-py3-none-any.whl |
|---|---|
| Size | 3.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7c92ab9d82a4dbdba551ed1afb97ea8dca678369458364ce97d373e7d8f190ea
|
|
BLAKE2b-256 checksum How to use checksums |
fb249d27a312c6261eb10380ce8e2f29dd71f1fc278353d7b178902847ecd3d6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.27.2
|
Security for uai 0.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.