📘 Day 16: break, continue, and the loop else clause

When you write a loop in Python you usually expect it to run from the first element to the last, doing the same block of code over and over.
Sometimes you need more control: stop early, skip the rest of the current iteration, or run a piece of code only if the loop wasn’t stopped early.
That’s what break, continue, and the loop‑else clause give you.

break – leaving the loop right now
When Python reaches a break, it immediately exits the innermost loop (whether for or while).
All remaining iterations are ignored, and execution continues with the first statement after the loop.

Why it works – A break raises a hidden internal exception that is caught by the loop machinery. The loop catches that exception, cleans up, and jumps out.

continue – skip to the next iteration
When Python sees a continue, it stops the current iteration right there and jumps to the top of the loop to evaluate the next item (or the loop condition again for a while). The code that follows continue inside the loop body is never run for that iteration.

Why it works – Internally Python raises a different hidden exception that tells the loop “start the next cycle now”. The loop catches it, skips the rest of the body, and proceeds.

else on a loop – run only if the loop finished normally
A loop can have an else block:

for item in iterable:
    # loop body
else:
    # runs when the loop **did NOT** encounter a break

The else block is executed after the loop finishes its natural course (i.e., the iterator is exhausted or the while condition became false). If a break occurs, the else block is skipped.

Why it works – After each iteration the loop checks two things:
1. Did we exit because of break? → skip else.
2. Did we run out of items / condition became false? → run else.

Putting it all together – a complete example

numbers = [5, 12, 7, -3, 0, 9, 4]

print("Scanning numbers...")

for n in numbers:
    # 1️⃣ Skip negative numbers – we don’t want to process them
    if n < 0:
        print(f"  {n} is negative → continue")
        continue                # jump to the next item

    # 2️⃣ Stop the whole scan as soon as we hit zero
    if n == 0:
        print("  Zero found! → break")
        break                   # leave the loop completely

    # Normal processing for positive, non‑zero numbers
    print(f"  {n} is ok, processing...")

else:
    # This runs only if we never hit the `break`
    print("All numbers processed without hitting zero.")

print("Done.")

Walk‑through

1. for n in numbers: – starts iterating over the list.
2. if n < 0: – detects a negative value.
continue prints a message and jumps to the next element, so the rest of the body (print of “ok”) is skipped for that iteration.
3. if n == 0: – when a zero appears, we print a message and break. The loop ends immediately, so the else block is not executed.
4. For any other positive number, we reach the regular print and continue looping.
5. If the loop runs through the whole list without ever hitting break, the else: block runs, confirming a “clean” finish.
6. Finally, print("Done.") runs after the loop (whether we broke out early or not).

What you’ll see when you run it

Scanning numbers...
  5 is ok, processing...
  12 is ok, processing...
  7 is ok, processing...
  -3 is negative → continue
  Zero found! → break
Done.

Notice that the else message never appears because we hit break at the zero.

When to use each construct

(continued below 👇)

- break – when a condition means “the rest of the work is pointless”. Typical examples: searching for an item, validating input, early exit on error.
- continue – when you want to ignore certain items but keep scanning the rest. Useful for filtering inside a loop without extra nesting.
- else on loops – when you need a “no‑break” confirmation. Common in search patterns: “found it → break; otherwise → after‑loop else means not found”.

Quick comparison

- break → stop the loop now.
- continue → skip the rest of this iteration, go to next.
- else → run after the loop only if no break happened.

Mastering these three tools lets you write loops that are both expressive and efficient, avoiding extra flags or nested conditionals.

📘 Day 17: Writing your first function (def, parameters, return)

def is the keyword that tells Python you are creating a function – a reusable block of code that can take parameters (inputs), do something, and optionally return a result.

Why use functions?
- Modularity – break a large program into smaller, manageable pieces.
- Reusability – call the same logic many times without rewriting it.
- Readability – give a meaningful name to a task, so the code reads like plain English.

When you write a function, three things happen behind the scenes:

1. Definition time – Python stores the function object under the name you give it. No code inside runs yet.
2. Call time – you use the name followed by parentheses, optionally passing arguments that match the parameters. Python creates a new local scope for that call.
3. Return – the return statement sends a value back to the caller and ends the function immediately. If you omit return, Python automatically returns None.

Step‑by‑step example

def greet(name):
    """
    Build a friendly greeting.
    The parameter `name` receives the caller's argument.
    """
    # Inside the function we create a local variable `message`.
    message = f"Hello, {name}!"   # f‑string inserts the value of `name`.
    return message               # Send `message` back to the caller.

# ---- calling the function ----
user_input = "Alice"             # This could come from anywhere.
result = greet(user_input)       # `user_input` is passed as an argument.
print(result)                    # Prints: Hello, Alice!

What each part does

- def greet(name): – Starts the definition. greet is the function name; name is a parameter that will receive a value when we call it.
- The triple‑quoted string right after the header is a docstring. It describes what the function does and can be accessed via greet.__doc__.
- message = f"Hello, {name}!" – A local variable; it exists only while this call runs. The f‑string formats the greeting by inserting the current value of name.
- return message – Sends the constructed string back to wherever the function was called. Execution of the function stops here.
- user_input = "Alice" – An ordinary variable holding the data we want to greet.
- result = greet(user_input) – Calling the function. user_input is an argument that gets bound to the parameter name. The function runs, returns the greeting, and that value is stored in result.
- print(result) – Uses the returned value just like any other variable.

Key points to remember

- Parameters vs. arguments – Parameters are the names in the function definition; arguments are the actual values you pass when calling.
- Scope – Variables created inside a function are local and disappear after the function returns. They do not affect variables with the same name outside.
- Return value – Only one return is executed per call. If you need to exit early, you can place return statements in conditional blocks.
- No return – If a function reaches the end without a return, Python automatically returns None, which is a special “nothing” object.

A slightly more complex function

def calculate_stats(numbers):
    """Return the sum and average of a list of numbers."""
    total = sum(numbers)               # built‑in sum adds all items
    average = total / len(numbers)     # len gives the count
    return total, average              # returns a tuple (total, average)

data = [4, 8, 15, 16, 23, 42]
sum_val, avg_val = calculate_stats(data)
print(f"Sum: {sum_val}, Average: {avg_val:.2f}")

(continued below 👇)

- Here calculate_stats takes one parameter numbers, which we expect to be an iterable of numeric values.
- The return total, average line actually returns a tuple containing both results. When we call the function, we can unpack that tuple directly into sum_val and avg_val.

By mastering def, parameters, and return, you now have the core tools to build any reusable piece of logic in Python. Practice by writing small functions that perform arithmetic, string manipulation, or data processing, and you’ll quickly see how they make your code cleaner and more powerful.

📘 Day 18: Default arguments and keyword arguments

Default arguments let you give a function parameter a value that will be used if the caller does not supply one. Keyword arguments let the caller specify a value by naming the parameter, so the order of the arguments can change.

When Python creates a function object, it stores the default values in a tuple called __defaults__. This tuple is built once, at function definition time, not each time the function runs. Because of that, the same object is reused for every call that omits the argument. This is why mutable defaults (like a list or dict) can keep state between calls – the object lives as long as the function object lives.

How the interpreter matches arguments

1. Positional arguments are matched to parameters in the order they appear.
2. Keyword arguments are matched by name, regardless of position.
3. After all positional arguments are assigned, any remaining parameters that have defaults get those defaults automatically.
4. If a parameter has no default and the caller didn’t provide a value, Python raises TypeError.

Why keyword arguments are powerful

- You can skip over optional parameters you don’t want to change.
- The call becomes self‑documenting: process(data, mode='fast') tells the reader what 'fast' means.
- They allow you to call a function with a subset of optional arguments without remembering the exact order.

Common pitfalls with mutable defaults

def append_to_log(message, log=[]):
    """Add a message to a growing log list."""
    log.append(message)
    return log

Calling this repeatedly:

print(append_to_log('first'))   # ['first']
print(append_to_log('second'))  # ['first', 'second']

What happened?
The list log is created once when append_to_log is defined. Each call re‑uses the same list, so it accumulates items across calls. This is often unintended.

Correct pattern – use None as the sentinel and create a new list inside the function:

def append_to_log(message, log=None):
    """Add a message to a fresh log list each call."""
    if log is None:
        log = []               # new list for this call
    log.append(message)
    return log

Now the calls are independent:

print(append_to_log('first'))   # ['first']
print(append_to_log('second'))  # ['second']

Full runnable example – mixing defaults and keywords

def greet(name, greeting='Hello', punctuation='!'):
    """
    Return a personalised greeting.
    * name        – required, positional or keyword
    * greeting    – optional, defaults to 'Hello'
    * punctuation – optional, defaults to '!'
    """
    return f"{greeting}, {name}{punctuation}"

# 1️⃣ Positional only
print(greet('Alice'))                         # Hello, Alice!

# 2️⃣ Positional + one keyword (out of order)
print(greet('Bob', punctuation='.' ))        # Hello, Bob.

# 3️⃣ All keywords – order doesn't matter
print(greet(name='Carol', punctuation='?', greeting='Hi'))  # Hi, Carol?

# 4️⃣ Mixing positional and keyword
print(greet('Dave', greeting='Good morning')) # Good morning, Dave!

Walk‑through

- def greet(name, greeting='Hello', punctuation='!'): defines two default arguments (greeting and punctuation).
- The function body builds a formatted string using the three parameters.
- In call 1, only name is supplied; the defaults fill in greeting and punctuation.
- In call 2, name and punctuation are given; greeting falls back to its default.
- In call 3, every argument is supplied by name, so the order can be shuffled.
- In call 4, name is positional, greeting is a keyword, and punctuation uses its default.

Quick checklist (bolded list)

(continued below 👇)

- Always place parameters with defaults after those without.
- Use None as a sentinel for mutable default values.
- Keyword arguments can be mixed with positional but must come after all positional arguments in the call.
- Defaults are evaluated once at definition time, not at each call.

📘 **Day 19: *args and **kwargs**

When you define a Python function, you usually list every parameter it expects:

```python
def greet(name, age):
print(f"Hello {name}, you are {age} years old.")
```

But real‑world functions often need **flexibility** – they may receive an unknown number of values or a set of named options that can change from call to call. That’s where `*args` and `**kwargs` come in.

**What `*args` does**
- The asterisk (`*`) before a parameter name tells Python *“collect any extra *positional* arguments into a tuple”*.
- Inside the function, `args` behaves exactly like any other tuple: you can iterate, index, or unpack it.

**What `**kwargs` does**
- The double asterisk (`**`) before a parameter name tells Python *“collect any extra *keyword* arguments into a dictionary”*.
- Inside the function, `kwargs` works like any dict: you can query keys, iterate over items, or use `.get()`.

**Why it works**
When a function call is evaluated, Python separates arguments into three groups:

1. **Positional arguments** that match the function’s regular parameters.
2. **Extra positional arguments** that don’t have a matching parameter – they go into `*args`.
3. **Keyword arguments** that match named parameters, plus any additional named arguments – the extras go into `**kwargs`.

Python builds `args` as a **tuple** because the order of positional arguments matters and they are immutable. It builds `kwargs` as a **dict** because each keyword must be unique and you need fast lookup by name.

**Calling a function with `*` and `**`**
The same symbols can be used *in reverse* when you **unpack** a sequence or mapping into a function call:

```python
values = (1, 2, 3)
options = {"verbose": True, "mode": "fast"}

def demo(a, b, c, verbose=False, mode="normal"):
print(a, b, c, verbose, mode)

demo(*values, **options) # expands to demo(1, 2, 3, verbose=True, mode="fast")
```

**Ordering rules**
When you mix regular parameters, `*args`, and `**kwargs` in a definition, the order must be:

```
def func(pos1, pos2, *args, kw1=None, kw2=None, **kwargs):
...
```

- Positional‑only (if using `/`), then normal positional, then `*args`, then keyword‑only, then `**kwargs`.

---

**Complete runnable example**

```python
def summarize(*numbers, **options):
"""
Prints a summary of any numeric values passed in,
and shows optional settings provided as keywords.
"""
# 1️⃣ *numbers is a tuple of all extra positional arguments
total = sum(numbers)
count = len(numbers)

# 2️⃣ **options is a dict of all extra keyword arguments
prefix = options.get("prefix", "Result")
show_average = options.get("average", False)

print(f"{prefix}:")
print(f" Count = {count}")
print(f" Sum = {total}")

if show_average and count > 0:
print(f" Avg = {total / count}")

# Calling with various combos
summarize(4, 7, 1, 3, prefix="Stats", average=True)
summarize(10, 20) # no extra keywords
summarize() # no numbers at all
```

**Walk‑through**

1. `def summarize(*numbers, **options):` –
- `*numbers` gathers **any number** of positional arguments into a tuple called `numbers`.
- `**options` gathers **any number** of keyword arguments into a dict called `options`.

2. Inside the function:
- `total = sum(numbers)` uses the built‑in `sum` on the tuple – works because tuples are iterable.
- `count = len(numbers)` gives how many numbers were passed.
- `options.get("prefix", "Result")` fetches the value for key `"prefix"` if present; otherwise defaults to `"Result"`.
- `options.get("average", False)` decides whether to display the average.

(continued below 👇)

3. The three calls demonstrate flexibility:
- The first call passes four numbers and two keywords (prefix and average).
- The second call passes only numbers, relying on default keyword values.
- The third call passes nothing; numbers becomes an empty tuple, options an empty dict, and the function still runs safely.

Key take‑aways

- *args packs extra positional arguments into a tuple.
- **kwargs packs extra keyword arguments into a dictionary.
- The same * and ** symbols unpack a sequence or mapping when calling a function.
- Using these constructs lets you write highly reusable and extensible functions without fixing the exact number or names of arguments up front.