coveo-styles
Don't let your CLI app spit out hundreds of boring lines!
Manage your user feedback a bit like you manage logs, and get bonus colors and emojis just because we can!
This module provides an echo symbol that you can use instead of print for convenience.
It is also completely customizable!
predefined themes for common actions
Here's how a ci run could look like:
from coveo_styles.styles import echo
echo.step("Launching ci operations")
echo.normal("pytest", emoji='hourglass')
echo.normal("black", emoji='hourglass')
echo.noise("Generated test reports in .ci/")
echo.success()
echo.warning("Formatting errors detected")
echo.suggest("The --fix switch will automatically fix these for you and re-run the test !!smile!!")
echo.error("The CI run detected errors you need to fix", pad_after=False)
echo.error_details("Black reported files to reformat", item=True)
echo.error_details("Details as items is nice!", item=True)
Launching ci operations
⌛ pytest
⌛ black
Generated test reports in .ci/
✔ Success!
⚠ Formatting errors detected
🤖 The --fix switch will automatically fix these for you and re-run the test 😄
💥 The CI run detected errors you need to fix
· Black reported files to reformat
· Details as items is nice
It's even nicer with colors! :) This doc needs a few animated gifs!
exception hook
Exception handlers may re-raise an exception as an ExitWithFailure in order to hide the traceback from the user and show a helpful error message.
Here's an example for the sake of demonstration:
from pathlib import Path
from coveo_styles.styles import ExitWithFailure
try:
project = Path('./project').read_text()
except FileNotFoundError as exception:
raise ExitWithFailure(suggestions='Use the --list switch to see which projects I can see') from exception
The stacktrace will be hidden, the app will exit with code 1 after printing the exception type and message:
! FileNotFoundError: [Errno 2] No such file or directory: 'project'
🤖 Use the --list switch to see which projects I can see
Unhandled exceptions (those that are not wrapped by an ExitWithFailure), will display the usual python feedback and stacktrace.
hunting for emojis
Emoji support is provided by the emoji package. Their description provides different links to help with your emoji hunt, but for some reason not everything is supported or has the name it should have.
The only foolproof way I have found is to actually inspect the emoji package, either by opening site-packages/emoji/unicode_codes/en.py in my IDE or programmatically like this:
from coveo_styles.styles import echo
from emoji.unicode_codes.en import EMOJI_UNICODE_ENGLISH, EMOJI_ALIAS_UNICODE_ENGLISH
query = 'smile'.lower()
for emoji_name in {*EMOJI_UNICODE_ENGLISH, *EMOJI_ALIAS_UNICODE_ENGLISH}:
emoji_name = emoji_name.strip(':')
if query in emoji_name.lower():
echo.normal(f'{emoji_name}: !!{emoji_name}!!')
sweat_smile: 😅
cat_face_with_wry_smile: 😼
smile: 😄
smiley: 😃
smiley_cat: 😺
smile_cat: 😸
Metadata
Release files for coveo-styles 4.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 |
|---|---|---|---|---|
| coveo_styles-4.0.tar.gz | 7.0 kB | With provenance | Details for coveo_styles-4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| coveo_styles-4.0-py3-none-any.whl | Python 3 | none | any | Details for coveo_styles-4.0-py3-none-any.whl |
Total release size: 14.4 kB
Release files / coveo_styles-4.0.tar.gz
| Download URL | coveo_styles-4.0.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4db3b8e0b07794cd21d842d71450b1f94fff49cde798095635ce5f7cbcec3875
|
|
BLAKE2b-256 checksum How to use checksums |
3c934fcc8673464de5208ff07ddb46e59e50f7eaff93f6d15bd01fff1545d20d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 13, 2026.
Transparency logRelease files / coveo_styles-4.0-py3-none-any.whl
| Download URL | coveo_styles-4.0-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
85779469d55c7d8d2e35f9963f469f81b12a06070cdb571c1f1dcf64186621ef
|
|
BLAKE2b-256 checksum How to use checksums |
293fad54ec24c9fb688e41bc463848aef87505e9f9d7e1128ab4e91e509b1b61
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 13, 2026.
Transparency logSecurity for coveo-styles 4.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for coveo_styles-4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 13, 2026.
Transparency logA 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.