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
Can we improve the <lambda>
in timed progress logging?
#300
Labels
bug
Something isn't working
Comments
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Feb 9, 2023
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Feb 9, 2023
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Feb 9, 2023
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Feb 9, 2023
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Feb 9, 2023
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Feb 9, 2023
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Feb 9, 2023
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Feb 14, 2023
phargogh
added a commit
to phargogh/pygeoprocessing
that referenced
this issue
Feb 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Whenever we have a bunch of long-running
raster_calculator()
calls, particularly when we're doing some multiprocessing, it's easy to end up with a whole pile of logging messages that look like this:Worse, even though many of these come from
raster_calculator
, the timed progress logging could really be coming from almost any one of the geoprocessing functions in the module. With python's ability to walk the call stack at runtime, we have to be able to programmatically and deliberately set the__name__
attribute to the calling function. So instead of seeing<lambda>
, we should seeraster_calculator
or maybe even a user-defined string if it's appropriate.The text was updated successfully, but these errors were encountered: