summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBonfaceKilz2022-05-26 13:04:20 +0300
committerBonfaceKilz2022-05-26 13:04:20 +0300
commita6dd5226f5b0b6a2e372fe9c2165d68715843c7e (patch)
treed1f2955ce9a02db984a82d28dfd1870694696404
parented86f415147e2b2936253abbdc0ba2a8d2704ab7 (diff)
downloadgn-gemtext-a6dd5226f5b0b6a2e372fe9c2165d68715843c7e.tar.gz
Move post on debugging with pudb into it's Topics
-rw-r--r--topics/using-pdb-to-troubleshoot.gmi (renamed from blog/2022-05-25-using-pdb.gmi)7
1 files changed, 2 insertions, 5 deletions
diff --git a/blog/2022-05-25-using-pdb.gmi b/topics/using-pdb-to-troubleshoot.gmi
index 6d9562a..06ac37a 100644
--- a/blog/2022-05-25-using-pdb.gmi
+++ b/topics/using-pdb-to-troubleshoot.gmi
@@ -1,11 +1,8 @@
# Using PDB to Troubleshoot Python Code
# Tags
-* date: 2022-05-17T00:00:00+03:00
-* draft: false
-* tags: debugging, python
-* author: bonfacem
-
+* type: documentation
+* keywords: debugging, python
Historically, debugging GeneNetwork code has been a bit of a pain where you would have `print' and `logging' statements to help view offending code chunks. This is not efficient, and we can do better! One painful side-effect wrt logging worth mentioning is that our logs grow quite fast and we need to rotate them, atm manually: