Merge lp://staging/~gary/launchpad/eggtarget into lp://staging/launchpad
Proposed by
Gary Poster
Status: | Merged |
---|---|
Merged at revision: | not available |
Proposed branch: | lp://staging/~gary/launchpad/eggtarget |
Merge into: | lp://staging/launchpad |
Diff against target: |
19 lines (+4/-1) 1 file modified
Makefile (+4/-1) |
To merge this branch: | bzr merge lp://staging/~gary/launchpad/eggtarget |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Tom Haddon | Approve | ||
Francis J. Lacoste (community) | Approve | ||
Review via email:
|
To post a comment you must log in.
This branch adds a target for the LOSAs to use to build eggs in such a way that they can be packaged up and copied elsewhere.
It is different from the current approach (``make bin/buildout && bin/buildout``) in two ways.
First, it silences the output of bin/buildout if there are no errors, which is nice, because building the eggs can produce some suspicious-looking output (having to do with Python 2.6 syntax tests, for instance) that shouldn't cause any worries unless buildout bails out.
Second and more importantly, it clears out the *.pyc files in the eggs. On the downside, this means that starting up the webservers will be slightly slower. On the upside, it means that the tracebacks in our OOPSes actually will contain a line of code for each frame run within the code of these eggs. We regard that as very important.
To test, ``make buildonce_eggs``. That will be the replacement line for ``bin/buildout && bin/buildout`` once this lands.
Thanks
Gary