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 default value in compute_domain #1586

Merged
merged 2 commits into from
Jan 22, 2020
Merged

Conversation

djrtwo
Copy link
Contributor

@djrtwo djrtwo commented Jan 22, 2020

Fixes #1582

Default value being passed into compute_domain was not being overridden when using alternative configuration files. Instead, default to None and conditionally set the variable if None to ensure get most updated version of config var

Thanks @benjaminion for reporting and solving the problem here!

@djrtwo djrtwo requested a review from protolambda January 22, 2020 14:26
@djrtwo djrtwo force-pushed the fix-default-compute-domain branch from a8a8018 to e821476 Compare January 22, 2020 18:39
"""
Return the domain for the ``domain_type`` and ``fork_version``.
"""
if fork_version is None:
Copy link
Collaborator

Choose a reason for hiding this comment

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

Looks good, however, with the new phase 1 changes the module is reloaded fully, instead of just reloading variables and type declarations. So this wouldn't be a problem in the future. Still think it is better practice to do this, and v0.10.1 needs it, so LGTM.

@protolambda protolambda merged commit 9f5f501 into v010x Jan 22, 2020
@protolambda protolambda deleted the fix-default-compute-domain branch January 22, 2020 23:29
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.

3 participants