Skip to content

[Feature] Improve Nox/Script Logging #68

@56kyle

Description

@56kyle

Is this for the template or generated projects?

Both

Feature Summary

Currently the nox sessions and CLI both have pretty varied logging amounts and quality. Most of the time this isn't too bad, but for first time setup it can leave users unsure whether anything is progressing if packages are being installed with no loading bar, or other similar scenarios where it seems to freeze due to first time installation/setup.

Example

Ideally we pipe through the preexisting logs that would occur during an installation / etc.

In some places this may just be removing some older try catch blocks and propagating errors, but in others it may require either custom feedthrough logic from dependency loggers into typer or making custom solutions.

Worst case scenario just adding tqdm as a dependency for the scripts is a possibility, but would definitely prefer to go for an approach that doesn't has us maintaining custom logging logic for CI tasks.

There are also a bunch of smaller improvements and general pockets of CLI just lacking indicators as to why/when things happen that would be super helpful to have tracked down and fixed.

Additional Context

Also worth mentioning if there is ever a release of the "robust-python" package or if this template gets a CLI built in then this problem will be offloaded. However, both of those ideas are pretty far out from being properly vetted/thought about.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions