From 5a35e7bf0f39ce93574837ddd887f6cfe75ff61b Mon Sep 17 00:00:00 2001 From: Semen Zhydenko Date: Fri, 16 Feb 2018 23:06:35 +0100 Subject: [PATCH 1/2] statments -> statements --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 20dd62b..a9679c6 100644 --- a/README.md +++ b/README.md @@ -84,7 +84,7 @@ Just give `ic()` a variable or expression and you're done. Easy. ### Plain Ice Cream (without Arguments) -Do you ever add print statments to determine which parts of your program are +Do you ever add print statements to determine which parts of your program are executed, and in which order they're executed? For example, if you've ever added prints statements to debug something like From 1337562a3a19c19916ff51025c52c46ad8c9b362 Mon Sep 17 00:00:00 2001 From: Semen Zhydenko Date: Fri, 16 Feb 2018 23:07:58 +0100 Subject: [PATCH 2/2] preceeding -> preceding --- icecream/icecream.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/icecream/icecream.py b/icecream/icecream.py index 6c09a93..38fcb7e 100644 --- a/icecream/icecream.py +++ b/icecream/icecream.py @@ -116,13 +116,13 @@ def getCallSourceLines(funcName, callFrame): def splitExpressionsOntoSeparateLines(source): """ - Split every expression onto its own line so any preceeding and/or trailing + Split every expression onto its own line so any preceding and/or trailing expressions, like 'foo(1); ' and '; foo(2)' of foo(1); ic(1); foo(2) are properly separated from ic(1) for dis.findlinestarts(). Otherwise, any - preceeding and/or trailing expressions break ic(1)'s bytecode offset + preceding and/or trailing expressions break ic(1)'s bytecode offset calculation with dis.findlinestarts(). """ indices = [expr.col_offset for expr in ast.parse(source).body]