-
Notifications
You must be signed in to change notification settings - Fork 2
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
Release 0.3 #28
Release 0.3 #28
Conversation
divvy/compute.py
Outdated
warnings.warn("Divvy compute configuration '{}' section changed " | ||
"to '{}'".format(old_compute_key, new_compute_key), | ||
DeprecationWarning) | ||
env_settings[new_compute_key] = env_settings[old_compute_key] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This way of handling the deprecation/backcompat allows the keys to map to different values.
warnings.warn("Divvy compute configuration '{}' section changed " | ||
"to '{}'".format(OLD_COMPUTE_KEY, NEW_COMPUTE_KEY), | ||
DeprecationWarning) | ||
env_settings[NEW_COMPUTE_KEY] = env_settings[OLD_COMPUTE_KEY] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It bothers me that this still allows subsequent mutations to have the keys get out of sync, but this is used in small enough fashion that I don't think it's a big deal. This sort of thing motivates pepkit/attmap#20.
Same as #28 (comment)
@nsheff I think this is set for merge now if you're ready |
great thanks! |
adds
divvy write
anddivvy list
commands, fixes yaml warnings, reduces verbosity.