Changelogs

• Use rich to track progress, instead of Halo
• Use rich for logging, instead of Loguru, to harmonize CLI output
• Scope logging configuration to the library
• Remove Loguru, tqdm, and Halo as dependencies

Adresses issue #255

Preview

Checklist:

• Was this PR discussed in an issue? It is recommended to first discuss a new feature into a GitHub issue before opening a PR.
• Add tests to cover the fixed bug(s) or the newly introduced feature(s) (if appropriate).
• Update the API documentation if a new function is added, or an existing one is deleted.
• Write concise and explanatory changelogs above.
• If possible, assign one of the following labels to the PR: feature, fix, chore, documentation or test (or ask a maintainer to do it for you).

When used in iPython, Halo raises an exception. The bug has been patched in their repo secven months ago, but no new release has been created since. The last release is more than four years old.

In order to fix this, I elected to use rich, a CLI formatting library that has progress trackers. It is up-to-date and well maintained. I replaced the ProgressIndicator class with a context manager function that wraps a Progress object from rich. In addition to a spinner, we also get progress bars. By using a ContextVar, we can nest multiple track_progress context manager, to track multiple tasks.

In order not to break the visual output in the CLI, I also used the logging handler provided by rich, replacing the Loguru library we had been using. I also took the opportunity to scope the logging configuration to the Polaris library logging only, to avoid changing any config the user might have set up in their code.