Skip to content

Conversation

takluyver
Copy link
Member

See #2149, #2715.

This roughly implements option 2 from Min's comment, which is what I'd expect from --all.

The alternative is to disable in only the first location where it is found enabled. I might even make that the default behaviour if we do that.

@takluyver takluyver added this to the 5.1 milestone Aug 4, 2017
def toggle_nbextension_python(self, module):
if self.all_config_locations:
for config_dir in jupyter_config_path():
disable_nbextension_python(self.section, module,
Copy link
Member

Choose a reason for hiding this comment

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

We should make sure this does:

if enabled at this level:
   set enabled = None # (not False. None pops config, False stores a value)
else:
   do nothing

So that it doesn't try to write any configuration files where there wasn't any to start with.

@takluyver
Copy link
Member Author

Closing in favour of #2729 .

@takluyver takluyver closed this Aug 7, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants