GTG needs a debug infrastructure
Bug #298202 reported by
Lionel Dricot
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GTG |
Fix Released
|
Wishlist
|
Bertrand Rousseau | ||
Bug Description
plutôt que de foutre des print partout, voir si ça vaudrait pas la peine d'utiliser un système de debug automatisé ou bien de créer notre propre fonction de debug (if DEBUG then print).
Bref, investiguer ce qui existe à ce niveau
| Changed in gtg: | |
| importance: | Undecided → Wishlist |
| Changed in gtg: | |
| status: | New → Confirmed |
Revision history for this message
| Jonathan Lange (jml) wrote | #1 |
| summary: |
- Framework de debug + Debug framework |
| summary: |
- Debug framework + GTG needs a debug infrastructure |
Revision history for this message
| Lionel Dricot (ploum-deactivatedaccount) wrote | #2 |
| Changed in gtg: | |
| assignee: | nobody → Bertrand Rousseau (bertrand-rousseau) |
| milestone: | none → 0.2 |
| status: | Confirmed → Fix Committed |
Revision history for this message
| Bertrand Rousseau (bertrand-rousseau) wrote | #3 |
| Changed in gtg: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Je parlais Français comme une vache Espagnole!
I'm guessing that this bug is suggesting that GTG needs a debugging framework. If so, using Python's builtin 'logging' module rather than 'if DEBUG then print' might be better, since that separates the events that need logging from the manner in which they are logged.