-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Base logging for progress meters #102
Comments
I have a prototype of this working at ProgressLogging. I started out intending to update ProgressMeter, but now it seems to me that the two packages actually provide very different functionality, and neither one can completely replace the other. |
It's compatible with the same command of Juno (shown above)? |
Yes, it works with that invocation. |
I started writing a comment here about how I think progress logging should work with the new infrastructure, and totally nerd sniped myself. Which led to the following implementation in In particular I'm quite excited about |
ProgressMeter is so great, thanks for this package that really helps the user experience in Juno. Is there any scope for Jupyter notebook support? |
There's such a thing in python so it's technically possible to do in the jupyter UI already. I don't know much about the technical details though. See https://github.com/tqdm/tqdm#ipython-jupyter-integration |
There is now https://github.com/JunoLab/ProgressLogging.jl which should be usable as a drop-in replacement of Juno. I also created https://github.com/tkf/ConsoleProgressMonitor.jl as a console-based backend for handling the log messages using ProgressMeter.jl. |
Base now has a way to log progress information. Juno is using:
This means that the standard logging setup can generate the logging information. It would be good if on v0.7 ProgressMeter.jl becomes simply a way of displaying this logging information. This way every package can natively support progress meters and how it is displayed just becomes a user-preference or IDE side issue.
This should be done in coordination with @pfitzseb and his work on Juno.
The text was updated successfully, but these errors were encountered: