Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates import and logger usage patterns across several modules to improve initialization order and ensure consistent access to configuration and logging utilities. The main focus is making sure that the
hazelbean.configmodule is imported early and used directly for logging, which helps avoid issues with uninitialized configuration variables.Key improvements include:
Initialization and Import Order:
hazelbean/__init__.pyto ensurehazelbean.configis imported before other modules, allowing configuration variables likeLAST_TIME_CHECKto be properly set for functions such ashb.timer(). [1] [2]Consistent Logger Usage:
hazelbean/geoprocessing_extension.pyandhazelbean/spatial_projection.pyto usehb_config.get_loggerandhb.config.get_loggerrespectively, ensuring loggers are consistently created via the configuration module rather than through the mainhbnamespace. [1] [2]Explicit Configuration Import:
hazelbean.configashb_configinhazelbean/geoprocessing_extension.pyfor clarity and to support the new logger usage pattern.