Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Better logging #231

Open
fmaussion opened this issue May 11, 2017 · 1 comment
Open

Better logging #231

fmaussion opened this issue May 11, 2017 · 1 comment
Milestone
2.x

Comments

@fmaussion
Copy link
Member

Currently, the loggers are used to print to stdout only. I think we should use options to allow logging to a file too.

Furthermore, it would be great to use the logger to redirect/copy warnings to a specific file, so that these warnings can be checked after a run.
@fmaussion fmaussion added this to the 1.x milestone Jul 7, 2017
@fmaussion
Copy link
Member Author

See #278

I think we should start to make OGGM loggers and OGGM error messager, which could nicely unify all our logging purposes and ensure a consistent output.

@fmaussion fmaussion modified the milestones: 1.1, 2.x Jun 14, 2018
@fmaussion fmaussion mentioned this issue Oct 12, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.x
Development

No branches or pull requests
1 participant
@fmaussion