-
-
Notifications
You must be signed in to change notification settings - Fork 202
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
default initialization of configurable traits from os.environ #158
Conversation
@@ -0,0 +1,88 @@ | |||
"""A dict-like table mapping keys to values based on indexing""" |
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.
Looks like this file was added by mistake.
2caab34
to
a981a0c
Compare
I've included
Having
Using |
a981a0c
to
80eedab
Compare
This seem to be stale a bit, and start to look like over engineering what traitlets can (and should do). So I'm curious if
Because that seem like quite a bit of maintenance for a potentialy really low use case, and we are spread thin, so I'm leaning toward "no new feature" at that point. |
@Carreau, should probably bring up whether this is needed in #157. As far as |
I'll close this one and make a new pr for |
Configurables hooks into a call from the metaclass to
setup_class
in order to setup default values fromos.environ
. This in turn callsTraitType.set_default_from_envvar
to apply that default value to the TraitType if the key'envvar'
is in its metadata.