Merge lp:~mvo/click/multiple-frameworks into lp:click
Status: | Merged |
---|---|
Approved by: | Colin Watson |
Approved revision: | 420 |
Merged at revision: | 421 |
Proposed branch: | lp:~mvo/click/multiple-frameworks |
Merge into: | lp:click |
Diff against target: |
370 lines (+221/-59) 6 files modified
click/build.py (+10/-22) click/framework.py (+135/-0) click/install.py (+8/-28) click/tests/helpers.py (+27/-0) click/tests/test_build.py (+39/-5) click/tests/test_install.py (+2/-4) |
To merge this branch: | bzr merge lp:~mvo/click/multiple-frameworks |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Colin Watson | Approve | ||
Review via email: mp+218280@code.launchpad.net |
Description of the change
This branch adds support for multiple frameworks in a click manifest.
To support multiple frameworks there is now a "click/
validate_
- the base version is the same for all frameworks used
- no additional relations like >= or similar is used in the framework declaration string
- no or dependencies (foo|bar) is used in the framework declaration string
It is possible to override if missing_frameworks is a error or a warning. Logging is used when this is overriden. I'm happy to use a different mechanism if logging is inappropriate.
The test helper gets a new click.test.
I currently use the pure-python version of click_framework
If there is anything else you would like me to change or do differently, please just let me know, happy to do it.
Thanks!
Michael
We ought to avoid exposing the CLICK_FRAMEWORK S_DIR environment variable interface when it's only for tests; tests should be able to install mock functions as appropriate to override the frameworks directory. And as you say the default framework directory should be generated by configure - I suspect that undoing the change to click/paths.py.in from r372.1.1 would be enough for this.
However, this doesn't need to block merging, and you can clean it up at your leisure. Other than that I see nothing to complain about here. Thanks!