Merge lp:~stevenk/launchpad/auditor-layer into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | Steve Kowalik on 2012-07-03 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 15540 |
| Proposed branch: | lp:~stevenk/launchpad/auditor-layer |
| Merge into: | lp:launchpad |
| Diff against target: |
219 lines (+119/-2) 6 files modified
buildout.cfg (+8/-0) lib/lp/services/auditor/server.py (+35/-0) lib/lp/services/auditor/tests/test_server.py (+28/-0) lib/lp/testing/layers.py (+43/-2) setup.py (+1/-0) versions.cfg (+4/-0) |
| To merge this branch: | bzr merge lp:~stevenk/launchpad/auditor-layer |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Benji York (community) | code | 2012-07-02 | Approve on 2012-07-02 |
|
Review via email:
|
|||
Commit Message
Add AuditorLayer and a server that the layer brings up, which allows us to start making use of auditor in code and tests.
Description of the Change
Add auditor and auditorfixture as depends (and Django, but let's not mention that fun fact at all), a layer and a server that the layer brings up. This allows us to start making use of auditor in code and tests.
| Benji York (benji) wrote : | # |
| Steve Kowalik (stevenk) wrote : | # |
The two Django's are there so that buildout actually works. The tarball is 'Django-
| Benji York (benji) wrote : | # |
> The two Django's are there so that buildout actually works. The tarball is
> 'Django-
> 'from django.something import else' so buildout looks for django, but it's
> Django, and so buildout goes bang.
Hmm, that's funny. In that case the branch looks good to me.

Why do you use setattr in the AuditorServer class's setUp method?
setattr(
[auditor] port)))
self, 'service_config',
dedent("""\
port: %d
""" % (self.config.
I would think this would work:
self. service_ config = ...
Under most conditions distribution names are case-insensitive so I am
curious why there are two Djangos in versions.cfg:
+django = 1.4
+Django = 1.4