no documention on how to debug launchpadlib request patterns.
Bug #583710 reported by
Robert Collins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| launchpadlib |
Triaged
|
High
|
Unassigned | ||
Bug Description
Leonard manages to show really lovely detailed traces of the requests that launchpadlib makes when talking about performance. I wants to knows how to do this myself - and for other users to be able to figure it out.
I suggest that launchpadlib/
Revision history for this message
| Robert Collins (lifeless) wrote | #1 |
Revision history for this message
| Gary Poster (gary) wrote | #2 |
| Changed in launchpadlib: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| summary: |
- debugging docs + no documention on how to debug launchpadlib request patterns. |
| tags: | added: trivial |
To post a comment you must log in.
20:52 < leonardr> sure
20:52 < leonardr> the simplest way to do it is:
20:52 < leonardr> import httplib2
20:52 < leonardr> httplib2.debuglevel = 1
20:52 < lifeless> how would you feel about that being in the docstring for launchpadlib/
20:53 < leonardr> sounds good
20:53 < lifeless> would you like me to propose a merge for that ?
20:53 < lifeless> or do you want to JFDI ? :)
20:53 < leonardr> sure. i can also put timing information in lazr.restfulclient that's controlled by httplib2.debuglevel or a separate debuglevel
20:53 < leonardr> httplib2's debuglevel won't give your elapsed time
20:53 < lifeless> ok