I probably will, but I'm still not 100% confident that I know the use-case for a docstring
versus a comment. The quick Google search I did was "comments explain how code works, docstrings
explain what a piece of code does" but that kind of sounds like the same thing to me?
Either way, documentation is super important and while I try to solve a lot of readability by
appropriatly naming variables/functions, somethings a note to myself (let alone someone else) is
really needed to make the code usable again in a timely manner a year/month/week/day later.
If we wanted to print up to and including the maximum value, should it fall appropriately
into the range (maximum = 100, for example, we might want to print 0,2,4,...,96,98,100)
we could make the max value in the range() function "maximum + 1" to make the endpoint
sort of pseudo-inclusive of that new target value.
It's not so much an uncertainty about ranges, but I always seem to run into an indexing problem
when utilizing ranges in a loop to iterate through a string or list or some array. I know I'm
probably going to have the problem, I try to plan around it, I still end up with the problem, so I
at least know where the issue lies when I have the inevitable error message.
I wasn't difficult to implement a for-loop for square.py because I do have some experience with programming
and replacing the same instructions with no conditionals or decision-making required was easy enough. I took the
repetitive pieces, counted them (squares have 4 sides) and used that as the basis for the instructions inside the loop,
then set the for-loop to iterate those four repetitions.
Pat Wick
pwick