From 75ef33bc87b191a5a6cac661b036c8b272a65b1b Mon Sep 17 00:00:00 2001 From: Arijit Sinha <110692661+crazymakibe@users.noreply.github.com> Date: Sat, 11 Jul 2026 22:05:28 +0530 Subject: [PATCH] Fix typo in DataFrame indexing exercise 7 hint --- notebooks/pandas/raw/ex_1.ipynb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/notebooks/pandas/raw/ex_1.ipynb b/notebooks/pandas/raw/ex_1.ipynb index fd6953ebd..51a62e3a8 100644 --- a/notebooks/pandas/raw/ex_1.ipynb +++ b/notebooks/pandas/raw/ex_1.ipynb @@ -511,7 +511,7 @@ "> `iloc` uses the Python stdlib indexing scheme, where the first element of the range is included and the last one excluded. \n", "`loc`, meanwhile, indexes inclusively. \n", "\n", - "> This is particularly confusing when the DataFrame index is a simple numerical list, e.g. `0,...,1000`. In this case `df.iloc[0:1000]` will return 1000 entries, while `df.loc[0:1000]` return 1001 of them! To get 1000 elements using `loc`, you will need to go one lower and ask for `df.iloc[0:999]`. " + "> This is particularly confusing when the DataFrame index is a simple numerical list, e.g. `0,...,1000`. In this case `df.iloc[0:1000]` will return 1000 entries, while `df.loc[0:1000]` return 1001 of them! To get 1000 elements using `loc`, you will need to go one lower and ask for `df.loc[0:999]`. " ] }, {