trac_uni
Convenient library to plug in tracer to incoming and outgoing points and extract data from there
Features
TODO
Credits
This package was created with Cookiecutter and the audreyr/cookiecutter-pypackage project template.
History
v0.0.2 (2018-12-24)
Bump version: 0.0.1 → 0.0.2 - finally tox works with all versions in PyCharm environment - starter tests for type and constants.
Bump version: 0.0.1 → 0.0.2.
Refab: - entry point rename.
Feat: - python 3.4 compatible named tuples for library options - starter constant - tested.
Refab: - some basic test to make 100% coverage.
Chore: - move interpreter version requirements from Pipfile into setup.py - turn on live log for py.test - return standard environment names in tox setup - set interpreter location for ‘py- charm’ in tox setup - fix python path passed in tox setup - edit doc according to 2 previous items.
Wip:
v0.0.1 (2018-12-21)
Bump version: 0.0.0 → 0.0.1 Project prepared for coding the tests.
Chore: - put into project current source to refab and test.
Chore: - changelog by git commits generation tool. [Konstantin Goncharov]
Docs: - short list what have been done to provide tooling.
Chore: - add make scripts for devpi - setup docs generation with browser refresh on changes - all make commands works. [Konstantin Goncharov]
Feat: - add primitive test - satisfy flake8. [Konstantin Goncharov]
Chore: - return template dev deps.
Chore: - install bumpversion dep - move pipfile loca index example in main file - add make script to generate requirements(_dev).txt.
Chore: - add devpi to make local repo builds - describe how to add devpi - provide files for run test in devpi environment. [Konstantin Goncharov]
v0.0.0 (2018-12-20)
Chore: - add description how to create this scaffolding - zeroed version.
Chore: - initialize python envs and deps.
Chore: - start from template.
Metadata
Release files for tracuni 0.4.18
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 |
|---|---|---|---|---|
| tracuni-0.4.18.tar.gz | 95.7 kB | Without provenance | Details for tracuni-0.4.18.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tracuni-0.4.18-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for tracuni-0.4.18-py2.py3-none-any.whl |
Total release size: 180.9 kB
Release files / tracuni-0.4.18.tar.gz
| Download URL | tracuni-0.4.18.tar.gz |
|---|---|
| Size | 95.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
127e30cb5405d8e998ea0a4400643c83afa33d06d62b85383ed3c0103e65f8bf
|
|
BLAKE2b-256 checksum How to use checksums |
382d99807ff9d954283344134b413e7abcf07da7d2fa71a390fb67ff19c83b35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / tracuni-0.4.18-py2.py3-none-any.whl
| Download URL | tracuni-0.4.18-py2.py3-none-any.whl |
|---|---|
| Size | 85.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
167a78684f0fecb95736d787283355a7a91bb9ca6165e93c922967ac1949b95b
|
|
BLAKE2b-256 checksum How to use checksums |
7277eed3171cde1337fcfb5583c7e790fe672106ee3edcc83e6b754e91a8a777
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for tracuni 0.4.18
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.