pyaux
Personal collection of helpers and often-useful snippets for Python
Install the latest version with pip install -U “git+https://gitlab.com/hoverhell/pyaux.git#egg=pyaux”
Contains:
window: iterator over a ‘window’ of N adjacent elements
dotdict: attr→item dict subclass (e.g. for d.key instead of d[‘key’])
DebugPlug: recursive duck-object for debug and testing purposes
repr_call: convenient syntactically-appropriate representation of call arguments (also used in DebugPlug)
fxrange, frange, dxrange, drange: xrange() / range() equivalents for float (without error accumulation) and Decimal
dict_fget, dict_fsetdefault: versions of dict.get and dict.setdefault with lazy-computation of the default value
split_list: simple one-pass splitting of list into two by a condition
use_cdecimal: forced instance-wide use (by monkey-hack) of cdecimal instead of decimal (for performance)
use_exc_ipdb: set unhandled exception handler to run ipdb.pm()
use_exc_log: set unhandled exception handler to log (by logging) the exception and the stack trace including (when possible) the local variables.
use_colorer: monkey-patch logging for colored logging
obj2dict: recursive converter of tree-structure of classes into a tree-structure of dicts, e.g. for pretty-printing the result
mk_logging_property: make a property that debug-logs the value and caller info when set
Some other things that are too minor to be listed here.
Also, in separate submodules:
psql: helpers for saving Django ORM objects into an SQL ‘COPY’-like file and loading it in one SQL command (for high-performance loading of large amounts of data into the database)
lzmah: lzma compress (as function and as an executable file); also provides a function unjsllzma to stream-read (json) lines from a pylzma-compressed file
lzcat: lzcat for pylzma-specific format (as function and as an executale file)
runlib: various things for runscripts:
init_logging: logging.basicConfig with useful defaults (for development runscripts).
sigeventer: list-based signal handler for SIGINT and SIGTERM (for appending handler functions, similarly to atexit)
Metadata
Release files for pyaux 5.1.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 |
|---|---|---|---|---|
| pyaux-5.1.1.tar.gz | 84.7 kB | Without provenance | Details for pyaux-5.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyaux-5.1.1-py3-none-any.whl | Python 3 | none | any | Details for pyaux-5.1.1-py3-none-any.whl |
Total release size: 182.2 kB
Release files / pyaux-5.1.1.tar.gz
| Download URL | pyaux-5.1.1.tar.gz |
|---|---|
| Size | 84.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f426f3081752080fec6efba73c2a003a6748edc3617f8ee41c7df2487435120d
|
|
BLAKE2b-256 checksum How to use checksums |
3093f79423f06c4ae9850c1fb00ccbe4ba5ee495a6410f6da92737f9f066c819
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.5
|
Release files / pyaux-5.1.1-py3-none-any.whl
| Download URL | pyaux-5.1.1-py3-none-any.whl |
|---|---|
| Size | 97.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c6e480ba3592248c893ce44fac608b5ddc65039308c60c4f8a64ed32625bc57d
|
|
BLAKE2b-256 checksum How to use checksums |
595730476d585a44efac8c20a0898abcc677b3a2d5f898936d5cd453ad6cc31b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.5
|
Security for pyaux 5.1.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.