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

Handle parameters that are 'None' in stage configuraitons in set_config. #67

Closed
eacharles opened this issue Apr 8, 2022 · 1 comment
Assignees

Comments

@eacharles
Copy link
Contributor

As it is now, if the default for a configuration parameter is not set (i.e., None) and the user tries to set it to None the code thinks that is has a missing parameter.

We need a way to distinguish this. As some level the issue is that the mechanism of definition of configuration parameters through config_options class data doesn't distinguish these cases.

@eacharles eacharles self-assigned this May 23, 2022
@joezuntz
Copy link
Collaborator

Closed by #73

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

No branches or pull requests

2 participants