Automatically enable extension dependencies
Review Request #1591 — Created May 14, 2010 and discarded
When extensions are enabled, extension dependencies are enabled. Two things: There's code from another review request in here (http://reviews.reviewboard.org/r/1590/) - that would be the extension_list changes, the djblets_extensions.py changes, and change #1 for base.py. Not entirely sure how to do individual branch changes, and have RB still like it.
- Description:
-
When extensions are enabled, extension dependencies are enabled.
Two things:
~ 1) There's code from another review request in here (http://reviews.reviewboard.org/r/1590/) - that would be the extension_list changes, the djblets_extensions.py changes, and change #1 for base.py. Not entirely sure how to do individual branch changes, and have RB still like it.
~ There's code from another review request in here (http://reviews.reviewboard.org/r/1590/) - that would be the extension_list changes, the djblets_extensions.py changes, and change #1 for base.py. Not entirely sure how to do individual branch changes, and have RB still like it.
- - 2) I'm posting this early and without tests as a "sneak preview", just to see if I've got the right idea, or to make early course corrections.
-
-
If we assume that every requirement is an extension, we're going to run into problems. For example, something that requires ReviewBoard, or Djblets, or RandomPythonPackage. We don't want those to have extension IDs or to be even known about. I think we should just require that extensions very explicitly list their requirements, and default this to []. If we require this, and we have the names be the extension IDs, then we don't need __id_from_requirement. We can just call enable_extension on the IDs themselves.
-
Can you rename to _get_id_from_requirement? The _ vs. __ makes a difference when it comes to debugging, as Python may mangle __.
-
-
-
-
-
-