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.

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

Fix handling of config for third party packages #169

Merged
merged 1 commit into from
Apr 15, 2022

Conversation

sfalmo
Copy link
Contributor

@sfalmo sfalmo commented Apr 6, 2022

Fix #168

There were some typos which led to wrong boolean values and a broken config mechanism.
Now the config works again and it is ensured that a third party package is only enabled if it is installed.

@michaelavs
Copy link
Contributor

@erogluorhan Would you mind looking this over? I believe everything looks good, but just want to be sure!

Copy link
Contributor

@michaelavs michaelavs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I successfully built and ran wrf-python with these updates and had the correct values returned. So, I am approving this PR in it's current state

@erogluorhan
Copy link
Collaborator

I successfully built and ran wrf-python with these updates and had the correct values returned. So, I am approving this PR in it's current state

Sounds good!

@michaelavs michaelavs merged commit 839e2ff into NCAR:develop Apr 15, 2022
@sfalmo sfalmo deleted the fix-config branch April 22, 2022 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Configuration routines for third party packages (enable_*(), disable_*(), *_enabled()) do not work
3 participants