Home Python Stack and Queue in Python Using Lists — How They Work and When to Use Each

Stack and Queue in Python Using Lists — How They Work and When to Use Each

In Plain English 🔥
Imagine a stack of dirty plates in the sink — you always wash the one on top, and you always add new dirty plates to the top too. That's a Stack: last in, first out. Now picture a line of people waiting at a coffee shop — the first person in line gets served first, and new people join at the back. That's a Queue: first in, first out. Both are just organised ways of controlling the order in which you process things.
⚡ Quick Answer
Imagine a stack of dirty plates in the sink — you always wash the one on top, and you always add new dirty plates to the top too. That's a Stack: last in, first out. Now picture a line of people waiting at a coffee shop — the first person in line gets served first, and new people join at the back. That's a Queue: first in, first out. Both are just organised ways of controlling the order in which you process things.

Every piece of software that feels responsive and organised under the hood is using some form of ordered data structure. Your browser's back button works because visited URLs are stored in a stack. Your print spooler sends documents to the printer in the exact order you sent them because it uses a queue. These aren't academic exercises — they're the backbone of real systems you interact with every day.

The problem both structures solve is deceptively simple: how do you control the order in which items are added and removed? A plain Python list lets you insert and delete from anywhere, which is powerful but dangerous when you need strict ordering. Stack and Queue impose rules on top of a list so your code can't accidentally process things in the wrong sequence. That constraint is the feature, not the limitation.

By the end of this article you'll know how to implement both a Stack and a Queue using nothing but Python's built-in list, understand exactly why each one exists, recognise the moment in a real project when you should reach for each one, and sidestep the subtle performance trap that catches almost every beginner who tries to build a Queue naively with a list.

The Stack — Last In, First Out Using a Python List

A Stack enforces one golden rule: the last item you put in is always the first item you take out. Computer scientists call this LIFO — Last In, First Out. Think of it like the undo history in a text editor. Every change you make gets pushed onto the stack. When you hit Ctrl+Z, the most recent change is popped off and reversed. You can never undo something from three steps ago without undoing the two steps in front of it first.

Python's list is a natural fit for a Stack because appending to the end is O(1) — it's blindingly fast. Removing from the end with pop() is also O(1). So both the core Stack operations — push and pop — cost basically nothing in time.

The key discipline is that you only ever touch one end of the list: the right end (the top of the stack). The moment you start inserting or removing from the middle or the left, you've broken the Stack contract and introduced bugs that will be very hard to trace.

browser_history_stack.py · PYTHON
1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556
# A Stack implemented with a Python list.
# Real-world scenario: browser back-button history.

class BrowserHistoryStack:
    def __init__(self):
        # The list acts as our stack storage.
        # The RIGHT end of the list is the TOP of the stack.
        self._history = []

    def push(self, url: str) -> None:
        """Visit a new page — push the URL onto the top of the stack."""
        self._history.append(url)  # append() is O(1) — always adds to the right end
        print(f"  Visited: {url}")

    def pop(self) -> str:
        """Go back — remove and return the most recently visited page."""
        if self.is_empty():
            raise IndexError("No history to go back to — stack is empty")
        previous_page = self._history.pop()  # pop() with no argument removes from the RIGHT end — O(1)
        print(f"  Going back to: {self._history[-1] if self._history else 'Start page'}")
        return previous_page

    def peek(self) -> str:
        """See the current page without removing it."""
        if self.is_empty():
            raise IndexError("Stack is empty — no current page")
        return self._history[-1]  # -1 index always gives us the top of the stack

    def is_empty(self) -> bool:
        return len(self._history) == 0

    def size(self) -> int:
        return len(self._history)

    def __repr__(self) -> str:
        # Display the stack so the top is on the RIGHT (most intuitive for lists)
        return f"BrowserHistoryStack({self._history}) <- TOP"


# --- Let's simulate a browsing session ---
history = BrowserHistoryStack()

history.push("https://google.com")
history.push("https://thecodeforge.io")
history.push("https://thecodeforge.io/python-stacks")

print(f"\nCurrent stack: {history}")
print(f"Currently on: {history.peek()}")
print(f"Stack size: {history.size()}")

print("\n-- Pressing back twice --")
history.pop()
history.pop()

print(f"\nCurrent stack: {history}")
print(f"Currently on: {history.peek()}")
▶ Output
Visited: https://google.com
Visited: https://thecodeforge.io
Visited: https://thecodeforge.io/python-stacks

Current stack: BrowserHistoryStack(['https://google.com', 'https://thecodeforge.io', 'https://thecodeforge.io/python-stacks']) <- TOP
Currently on: https://thecodeforge.io/python-stacks
Stack size: 3

-- Pressing back twice --
Going back to: https://thecodeforge.io
Going back to: https://google.com

Current stack: BrowserHistoryStack(['https://google.com']) <- TOP
Currently on: https://google.com
⚠️
Pro Tip:Always guard your pop() and peek() with an is_empty() check. A bare list.pop() on an empty list throws an IndexError with no helpful context. Wrapping it in a class and raising a descriptive error saves you 20 minutes of debugging later.

The Queue — First In, First Out Using a Python List (and Why Naive Lists Are Slow)

A Queue enforces the opposite rule: the first item in is the first item out — FIFO. Think of tickets in a support system. The customer who raised a ticket first should get helped first. Nobody skips the line.

Here's where Python beginners hit a wall. You might assume you can just use list.insert(0, item) to add to the front and list.pop() to remove from the back — or append() to add to the back and pop(0) to remove from the front. Both approaches work correctly but the pop(0) or insert(0, ...) operations are O(n). Every time you remove from the front of a Python list, Python has to shift every remaining element one position to the left in memory. On a list with 100,000 items, that's 100,000 memory operations for a single dequeue. This kills performance.

For a true production Queue, Python's standard library gives you collections.deque (double-ended queue) which solves this in O(1). But understanding the list-based version first is essential — it's the foundation, and it's what interviewers test you on to see if you understand the underlying cost.

support_ticket_queue.py · PYTHON
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081
# A Queue implemented with a Python list.
# Real-world scenario: customer support ticket processing.
# We'll also benchmark the naive approach to show WHY deque exists.

import time

class SupportTicketQueue:
    def __init__(self):
        # The list acts as our queue storage.
        # RIGHT end = back of queue (where new tickets are added).
        # LEFT end  = front of queue (where tickets are processed next).
        self._tickets = []

    def enqueue(self, ticket_id: str) -> None:
        """Add a new support ticket to the back of the queue."""
        self._tickets.append(ticket_id)  # append() is O(1) — fast
        print(f"  Ticket {ticket_id} added to queue")

    def dequeue(self) -> str:
        """Process the next ticket — remove from the front of the queue."""
        if self.is_empty():
            raise IndexError("No tickets in queue — nothing to process")
        # pop(0) removes the FIRST element — but this is O(n) on a plain list!
        # Every element shifts left by one position in memory.
        # This is fine for small queues; use collections.deque for large ones.
        next_ticket = self._tickets.pop(0)
        print(f"  Processing ticket: {next_ticket}")
        return next_ticket

    def peek(self) -> str:
        """See which ticket is next without processing it."""
        if self.is_empty():
            raise IndexError("Queue is empty")
        return self._tickets[0]  # Front of the queue is always index 0

    def is_empty(self) -> bool:
        return len(self._tickets) == 0

    def size(self) -> int:
        return len(self._tickets)

    def __repr__(self) -> str:
        return f"FRONT -> {self._tickets} <- BACK"


# --- Simulate a support queue ---
ticket_queue = SupportTicketQueue()

ticket_queue.enqueue("TKT-001")  # First customer — should be helped first
ticket_queue.enqueue("TKT-002")
ticket_queue.enqueue("TKT-003")

print(f"\nQueue state: {ticket_queue}")
print(f"Next up: {ticket_queue.peek()}")
print(f"Tickets waiting: {ticket_queue.size()}")

print("\n-- Processing tickets in order --")
ticket_queue.dequeue()  # TKT-001 goes first — FIFO in action
ticket_queue.dequeue()  # TKT-002 goes second

print(f"\nQueue state: {ticket_queue}")

# --- Now let's see the O(n) cost of pop(0) on a large list ---
print("\n-- Performance comparison: pop(0) vs pop() --")

large_list_front = list(range(500_000))  # 500,000 items
large_list_back  = list(range(500_000))

start = time.perf_counter()
for _ in range(10_000):
    large_list_front.pop(0)  # Removing from the FRONT — O(n) each time
elapsed_front = time.perf_counter() - start

start = time.perf_counter()
for _ in range(10_000):
    large_list_back.pop()    # Removing from the BACK — O(1) each time
elapsed_back = time.perf_counter() - start

print(f"  pop(0) — removing from front: {elapsed_front:.4f}s")
print(f"  pop()  — removing from back:  {elapsed_back:.4f}s")
print(f"  pop(0) is roughly {elapsed_front / elapsed_back:.1f}x slower")
▶ Output
Ticket TKT-001 added to queue
Ticket TKT-002 added to queue
Ticket TKT-003 added to queue

Queue state: FRONT -> ['TKT-001', 'TKT-002', 'TKT-003'] <- BACK
Next up: TKT-001
Tickets waiting: 3

-- Processing tickets in order --
Processing ticket: TKT-001
Processing ticket: TKT-002

Queue state: FRONT -> ['TKT-003'] <- BACK

-- Performance comparison: pop(0) vs pop() --
pop(0) — removing from front: 0.3821s
pop() — removing from back: 0.0008s
pop(0) is roughly 477.6x slower
⚠️
Watch Out:Never use a plain list as a Queue in performance-sensitive code. The benchmark above shows pop(0) can be 400-500x slower than pop() on large lists. Switch to collections.deque — it's designed for O(1) appends and pops from both ends, making it the correct Queue implementation in Python.

When to Use a Stack vs Queue — Real Patterns You'll Actually Encounter

Knowing the mechanics is only half the battle. The real skill is recognising which structure fits the problem in front of you. Here's a reliable mental model: if your problem is about reversing, unwinding, or backtracking — use a Stack. If your problem is about maintaining order of arrival and processing things fairly — use a Queue.

Stacks show up in: undo/redo systems, function call management (the call stack is literally a stack), balanced bracket validation in parsers, depth-first graph traversal, and expression evaluation in calculators.

Queues show up in: task scheduling, print spoolers, breadth-first graph traversal, request handling in web servers, rate limiters, and any producer-consumer pipeline where you want to process work in arrival order.

The example below shows bracket validation — a Stack-based algorithm that appears constantly in coding interviews and real compilers. It's a perfect illustration because the stack's LIFO property is exactly what lets you match the most recently opened bracket first.

bracket_validator_stack.py · PYTHON
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354
# Real-world Stack use case: validating balanced brackets.
# This exact logic is used in code editors, compilers, and JSON parsers.

def is_balanced(expression: str) -> bool:
    """
    Returns True if all brackets in the expression are correctly matched.
    Uses a Stack to track open brackets as we scan left to right.
    """
    # Map each closing bracket to its expected opening bracket
    matching_open = {')': '(', ']': '[', '}': '{'}
    closing_brackets = set(matching_open.keys())
    opening_brackets = set(matching_open.values())

    bracket_stack = []  # Our stack — stores unmatched opening brackets

    for character in expression:
        if character in opening_brackets:
            # We found an opener — push it onto the stack and move on
            bracket_stack.append(character)

        elif character in closing_brackets:
            # We found a closer — the stack top MUST be its matching opener
            if not bracket_stack:
                # Closer with nothing on the stack — unmatched closer
                return False

            top_of_stack = bracket_stack.pop()  # Pop the most recent opener

            if top_of_stack != matching_open[character]:
                # Top of stack doesn't match this closer — mismatched pair
                return False

    # If the stack is empty, every opener was matched and closed
    # If not empty, some openers were never closed
    return len(bracket_stack) == 0


# --- Test the validator ---
test_cases = [
    ("({[]})",          True),   # Perfectly nested — all matched
    ("([)]",            False),  # Wrong order — square closed before round
    ("{[()()]}",        True),   # Multiple levels of nesting — all matched
    ("(((",             False),  # All openers, no closers
    (")))",             False),  # All closers, no openers
    ("def func(a[0]):", True),   # Real code-like expression
    ("{name: [1,2,3]}", True),   # JSON-like structure
]

print("Bracket Validation Results:")
print("-" * 45)
for expression, expected in test_cases:
    result = is_balanced(expression)
    status = "PASS" if result == expected else "FAIL"
    print(f"  [{status}] '{expression}' -> {result}")
▶ Output
Bracket Validation Results:
---------------------------------------------
[PASS] '({[]})' -> True
[PASS] '([)]' -> False
[PASS] '{[()()]}' -> True
[PASS] '(((' -> False
[PASS] ')))' -> False
[PASS] 'def func(a[0]):' -> True
[PASS] '{name: [1,2,3]}' -> True
🔥
Interview Gold:The bracket validation algorithm is one of the top 10 most common Stack interview questions. Notice how the Stack's LIFO order is not just incidental — it's the entire reason the algorithm works. Being able to articulate that connection (not just write the code) is what separates a good answer from a great one.
Feature / AspectStack (LIFO)Queue (FIFO)
Order principleLast In, First OutFirst In, First Out
Add operation namepush — append() → O(1)enqueue — append() → O(1)
Remove operation namepop — list.pop() → O(1)dequeue — list.pop(0) → O(n) ⚠️
Which end is active?Only the right/top endAdd to right, remove from left
Best Python implementationlist (built-in)collections.deque (standard lib)
Typical use casesUndo, call stack, DFS, parsersTask queues, BFS, scheduling
Peek operation costO(1) — list[-1]O(1) — list[0]
Risk with plain listNone — both ops are O(1)pop(0) is O(n) — use deque instead
Real-world analogyStack of platesCoffee shop line

🎯 Key Takeaways

  • A Stack uses LIFO order — list.append() to push and list.pop() to pop, both O(1). The right end of the list is the top. Never touch the left end.
  • A plain Python list-based Queue is correct but slow — list.pop(0) is O(n). For any production Queue, use collections.deque with appendleft()/popleft() or append()/popleft() for true O(1) performance.
  • Reach for a Stack when your problem involves backtracking, unwinding, or reversing (undo systems, DFS, bracket matching). Reach for a Queue when order of arrival matters (task scheduling, BFS, rate limiting).
  • The bracket validation algorithm is a must-know Stack interview pattern — practise explaining WHY the LIFO property is what makes it work, not just how to code it.

⚠ Common Mistakes to Avoid

  • Mistake 1: Using pop(0) for a Queue in a loop on large datasets — Symptom: code works correctly but becomes noticeably slow as the list grows, eventually freezing on datasets above ~50,000 items — Fix: replace list.pop(0) with collections.deque and use popleft() instead, which is O(1) and designed exactly for this purpose.
  • Mistake 2: Confusing which end is the 'top' of the Stack — Symptom: the Stack works but the items come out in the wrong order because you're mixing append() with pop(0), or insert(0,...) with pop() — Fix: commit to one convention: always use list.append() to push and list.pop() (no argument) to pop. The right end of the list is always the top of the stack.
  • Mistake 3: Not guarding pop() and peek() on empty structures — Symptom: IndexError with a confusing traceback pointing inside your class rather than to the calling code — Fix: always check is_empty() before any removal or peek operation and raise a descriptive exception yourself, e.g. raise IndexError('Cannot pop from an empty stack') so the error message tells you exactly what went wrong.

Interview Questions on This Topic

  • QWhat is the time complexity of enqueue and dequeue when you implement a Queue using a plain Python list, and how would you fix any performance issue you find? (Tests whether you know pop(0) is O(n) and that collections.deque is the correct solution.)
  • QCan you implement a Stack that supports push, pop, peek, and a get_minimum() operation — all in O(1) time? (Classic interview problem — the trick is maintaining a second 'min stack' in parallel that tracks the minimum at every level.)
  • QYou have a Stack. Using only push and pop operations on that Stack (no extra arrays), how would you reverse the order of all its elements? (Tricky follow-up — answer requires a recursive approach or using a second temporary stack, and tests whether you truly understand LIFO.)

Frequently Asked Questions

Should I use a Python list or collections.deque to implement a Queue?

Use collections.deque for any real Queue. A plain list works correctly but list.pop(0) — the dequeue operation — is O(n) because Python shifts every remaining element in memory. deque.popleft() is O(1). For learning or tiny datasets the list is fine; for anything in production, use deque.

What is the difference between a Stack and a Queue in Python?

A Stack is LIFO — the last item you add is the first one you remove, like a stack of plates. A Queue is FIFO — the first item you add is the first one you remove, like a waiting line. Both can be built on a Python list, but the direction you add and remove items is opposite.

Why does Python not have a built-in Stack class?

Because a plain Python list already behaves as a perfect Stack out of the box. list.append() is push and list.pop() is pop — both are O(1). There's no need for a separate class. If you want a formal interface with named methods and safety guards, you wrap the list in your own class, which is exactly what the examples in this article do.

🔥
TheCodeForge Editorial Team Verified Author

Written and reviewed by senior developers with real-world experience across enterprise, startup and open-source projects. Every article on TheCodeForge is written to be clear, accurate and genuinely useful — not just SEO filler.

← PreviousString Methods in PythonNext →Functions in Python
Forged with 🔥 at TheCodeForge.io — Where Developers Are Forged