14,695,505 members
1.00/5 (1 vote)
See more:
My objective is to derive a function that prints the no of lowercase characters and uppercase characters. I tried to find out but couldn't

What I have tried:

What is wrong in this code?
find out please help
```def determine_upper_lower(value):
upper_case = 0
lower_case = 0

for i in value:
if i.isupper():
upper_case = upper_case + 1

elif i.islower():
lower_case = lower_case + 1

result = 'the number of uppercase letters are ' + str(upper_case) + ' and the number of lowercase letters are ' + str(lower_case)
return result

sample_string = 'Quick brown fox jumped over the lazy Dog'
print(determine_upper_lower(sample_string)```
Posted
Updated 7-Sep-20 1:20am
v2

## Solution 2

Indentation.
Proper indentation of code is mandatory in `Python`.
The Automatic Code Fix Tool© produced:
```def determine_upper_lower(value):
upper_case = 0
lower_case = 0

for i in value:
if i.isupper():
upper_case = upper_case + 1
elif i.islower():
lower_case = lower_case + 1

result = 'the number of uppercase letters are ' + str(upper_case) + ' and the number of lowercase letters are ' + str(lower_case)
return result

sample_string = 'Quick brown fox jumped over the lazy Dog'
print(determine_upper_lower(sample_string))```
v2

## Solution 1

In Python, indentation is important: it's used to mark a block of statements.
So if you say this:
```if a != b:
c = a + 1
c = c + b
print(c)```
then both assignments are only executed if a and b are different
If you say this:
```if a != b:
c = a + 1
c = c + b
print(c)```
Then the second assignment is always executed.

You code is flat to the left: it won't work because it's expecting
`upper_case = 0`
to be indented as part of the function body.

Assuming you fix the indentation so your code runs, you then need to test it and fix any problems. Think of the development process as writing an email: a lack of syntax errors means that you wrote the email in the right language - English, rather than German for example - not that the email contained the message you wanted to send.

So now you enter the second stage of development (in reality it's the fourth or fifth, but you'll come to the earlier stages later): Testing and Debugging.

Start by looking at what it does do, and how that differs from what you wanted. This is important, because it give you information as to why it's doing it. For example, if a program is intended to let the user enter a number and it doubles it and prints the answer, then if the input / output was like this:
```Input   Expected output    Actual output
1            2                 1
2            4                 4
3            6                 9
4            8                16```
Then it's fairly obvious that the problem is with the bit which doubles it - it's not adding itself to itself, or multiplying it by 2, it's multiplying it by itself and returning the square of the input.
So with that, you can look at the code and it's obvious that it's somewhere here:
```def Double(value):
return value * value```

Once you have an idea what might be going wrong, start using the debugger to find out why. Put a breakpoint on the first line of the method, and run your app. When it reaches the breakpoint, the debugger will stop, and hand control over to you. You can now run your code line-by-line (called "single stepping") and look at (or even change) variable contents as necessary (heck, you can even change the code and try again if you need to).
Think about what each line in the code should do before you execute it, and compare that to what it actually did when you use the "Step over" button to execute each line in turn. Did it do what you expect? If so, move on to the next line.
If not, why not? How does it differ?
Hopefully, that should help you locate which part of that code has a problem, and what the problem is.
This is a skill, and it's one which is well worth developing as it helps you in the real world as well as in development. And like all skills, it only improves by use!

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Top Experts
Last 24hrsThis month
 OriginalGriff 250 RickZeeland 120 Rick York 100 Richard Deeming 100 Sandeep Mewara 100
 OriginalGriff 6,079 Richard Deeming 3,165 Richard MacCutchan 2,824 CPallini 2,012 Patrice T 1,650

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900