-
-
Notifications
You must be signed in to change notification settings - Fork 402
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
Introduce standard point for enabling/disabling features #1041
Comments
Agree with the overall proposal, not entirely happy with |
I'm not particularly attached to the name |
This does seem like a top-level concept to me. |
Sure, I'm overruled 😄 |
Ok, any suggestions for the name of this thing? |
|
I suppose a Even then I'm not 100% convinced as it sounds like it is enabling/disabling features whereas it is more about enabling/disabling versions of various features. Need to think about it more. |
How about I quite like this as I can't think of anything else we want to configure other than backwards compatibility settings - everything notebook specific is done by the notebook extension. |
Fine by me. |
Same here, |
This has now been added, closing. |
Just to keep a record, |
It would be good to have a convenient place to enable/disable particular holoviews features. This would help by allowing us to encourage uses to use new behavior (for instance the recently enabled changes to layouts) before they are on by default or to re-enable old behaviors for backwards compatibility.
This system should be tied to versions in some way. I've not thought through the API yet, but something like:
Maybe calling
hv.enable()
(i.e without arguments) could print a list of options to enable/disable. I think it would be good to introduce this system for 1.7.The text was updated successfully, but these errors were encountered: