Stack: LIFO order using list.append() and list.pop() — both O(1) operations
Queue: FIFO order with list.append() and list.pop(0) — pop(0) is O(n) due to element shifting
Production queue: use collections.deque for O(1) popleft() on both ends
Bracket validation is the classic stack interview problem — LIFO is the algorithm's core
Most common mistake: using list.pop(0) in a loop — performance drops 400x on large datasets
Plain-English First
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.pyPYTHON
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
# A Stack implemented with a Python list.# Real-world scenario: browser back-button history.classBrowserHistoryStack:
def__init__(self):
# The list acts as our stack storage.# The RIGHT end of the list is the TOP of the stack.self._history = []
defpush(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 endprint(f" Visited: {url}")
defpop(self) -> str:
"""Go back — remove and return the most recently visited page."""ifself.is_empty():
raiseIndexError("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
defpeek(self) -> str:
"""See the current page without removing it."""ifself.is_empty():
raiseIndexError("Stack is empty — no current page")
return self._history[-1] # -1 index always gives us the top of the stackdefis_empty(self) -> bool:
returnlen(self._history) == 0defsize(self) -> int:
returnlen(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.
Production Insight
Using a list as a stack is production-safe — both append and pop are O(1).
The real risk is accidentally inserting at index 0, which breaks the LIFO contract and causes subtle ordering bugs.
Rule: never use insert(0) or pop(0) on a stack — they destroy the structure's invariant.
Key Takeaway
Stack with list: append for push, pop() for pop.
Both O(1). Never touch the left end.
The simplicity is the feature — don't overcomplicate it.
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.pyPYTHON
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
# 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
classSupportTicketQueue:
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 = []
defenqueue(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) — fastprint(f" Ticket {ticket_id} added to queue")
defdequeue(self) -> str:
"""Process the next ticket — remove from the front of the queue."""ifself.is_empty():
raiseIndexError("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
defpeek(self) -> str:
"""See which ticket is next without processing it."""ifself.is_empty():
raiseIndexError("Queue is empty")
return self._tickets[0] # Front of the queue is always index 0defis_empty(self) -> bool:
returnlen(self._tickets) == 0defsize(self) -> int:
returnlen(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 secondprint(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 _ inrange(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 _ inrange(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.
Production Insight
list.pop(0) is O(n) because every remaining element shifts left in memory.
On a list of 500k items, 10k dequeue operations can be 400x slower than pop() from the right.
Rule: for production queues, import deque — it's in the standard library for this exact reason.
Key Takeaway
Queue with list: enqueue is O(1), dequeue is O(n).
deque solves the O(n) problem with O(1) popleft().
Never use list.pop(0) in production — it's a performance trap.
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.pyPYTHON
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
# Real-world Stack use case: validating balanced brackets.# This exact logic is used in code editors, compilers, and JSON parsers.defis_balanced(expression: str) -> bool:
"""
ReturnsTrueif 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 bracketsfor 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 openerifnot bracket_stack:
# Closer with nothing on the stack — unmatched closerreturnFalse
top_of_stack = bracket_stack.pop() # Pop the most recent openerif top_of_stack != matching_open[character]:
# Top of stack doesn't match this closer — mismatched pairreturnFalse# If the stack is empty, every opener was matched and closed# If not empty, some openers were never closedreturnlen(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.
Production Insight
The bracket validator works because LIFO matches the most recently opened bracket first — that's the stack's identity.
Parsers in linters, compilers, and IDEs use this exact logic daily.
Rule: when you need to pair recent items first, think stack — every other approach is harder to reason about.
Key Takeaway
Stack is for backtracking (undo, parsing, DFS).
Queue is for fair ordering (task queues, BFS, scheduling).
The structure's order rule is not incidental — it's the entire solution.
Choose Between Stack and Queue: A Decision Tree
IfNeed to undo/reverse or track backtracking steps
→
UseUse a Stack (LIFO). Examples: undo, bracket validator, DFS.
IfNeed to process items in the exact order they arrived
→
UseUse a Queue (FIFO). Examples: ticket system, BFS, print queue.
IfBoth dimension needed (order of arrival and recency)
→
UseUse a Deque with separate policy, or combine a queue and a stack.
From Naive List to Production-Grade Queue: Why deque Exists
When you benchmark list.pop(0) against deque.popleft(), the difference is staggering. A deque (double-ended queue) is implemented as a doubly-linked list under the hood — every append and pop from either end is O(1). There's no memory shifting. That's why the standard library provides it.
Switching from a list-based queue to deque is just a two-line change: replace your list with deque(), and replace pop(0) with popleft(). The rest of your code stays the same. Do it before your queue grows beyond a few thousand items.
The example below shows a direct replacement for the support ticket queue, plus a benchmark confirming O(1) performance.
deque_queue.pyPYTHON
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
# Production-grade Queue using collections.dequefrom collections import deque
import time
classDequeQueue:
def__init__(self):
self._items = deque()
defenqueue(self, item):
self._items.append(item) # O(1)defdequeue(self):
ifnotself._items:
raiseIndexError("Queue empty")
return self._items.popleft() # O(1) — no element shiftingdefpeek(self):
ifnotself._items:
raiseIndexError("Queue empty")
returnself._items[0]
defis_empty(self):
returnlen(self._items) == 0def__len__(self):
returnlen(self._items)
# --- Benchmark: deque popleft() vs list pop(0) ---import time
deque_bench = deque(list(range(500_000)))
list_bench = list(range(500_000))
start = time.perf_counter()
for _ inrange(10_000):
deque_bench.popleft()
elapsed_deque = time.perf_counter() - start
start = time.perf_counter()
for _ inrange(10_000):
list_bench.pop(0)
elapsed_list = time.perf_counter() - start
print(f"deque.popleft(): {elapsed_deque:.6f}s")
print(f"list.pop(0): {elapsed_list:.6f}s")
print(f"deque is about {elapsed_list / elapsed_deque:.0f}x faster")
Output
deque.popleft(): 0.000244s
list.pop(0): 0.193210s
deque is about 792x faster
Drop-in Replacement:
You can replace a list-based queue with deque without changing your API. Just import deque, initialise with deque() instead of [], replace pop(0) with popleft(), and you're done. No other code changes needed.
Production Insight
deque.popleft() is O(1) — the same constant time regardless of queue size.
The benchmark on 500k items shows a 792x speedup over list.pop(0).
Rule: any queue in production should use deque. It's that simple.
Key Takeaway
deque is the correct tool for FIFO queues.
list.pop(0) is a bug waiting to happen under load.
Import deque before you need it — don't wait for the slowdown.
Stack and Queue in Python's Standard Library: Where They Already Live
You don't always need to roll your own. Python's standard library already has full implementations for both patterns:
collections.deque can be used as a stack (append/pop) or a queue (append/popleft).
queue.Queue is thread-safe and blocks on empty/full — perfect for producer-consumer patterns.
queue.LifoQueue is a thread-safe stack.
queue.PriorityQueue orders items by priority (min-heap).
Python's call stack itself is a stack — each function call pushes a frame, and returns pop it. That's why deep recursion hits a RecursionError — the stack overflows.
The code below shows how to use queue.Queue for a multi-threaded worker queue, the kind you'd use in a real web scraper or batch processor.
threaded_queue.pyPYTHON
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
# Thread-safe worker queue using queue.Queuefrom queue importQueuefrom threading importThreadimport time
defworker(work_queue: Queue, worker_id: int):
whileTrue:
item = work_queue.get()
if item is None: # poison pill to stop the worker
work_queue.task_done()
breakprint(f"Worker {worker_id} processing: {item}")
time.sleep(0.1) # simulate work
work_queue.task_done()
# Create a queue with maximum 10 pending items
q = Queue(maxsize=10)
# Start 3 worker threads
threads = []
for i inrange(3):
t = Thread(target=worker, args=(q, i))
t.start()
threads.append(t)
# Enqueue 20 tasksfor i inrange(20):
q.put(f"Task-{i}")
print(f"Enqueued Task-{i}, queue size: {q.qsize()}")
# Wait for all tasks to be processed
q.join()
# Stop workers with poison pillsfor _ inrange(3):
q.put(None)
for t in threads:
t.join()
print("All tasks completed.")
Output
Enqueued Task-0, queue size: 1
Enqueued Task-1, queue size: 2
...
Worker 0 processing: Task-0
Worker 1 processing: Task-1
Worker 2 processing: Task-2
...
All tasks completed.
When to Use Queue vs Deque:
Use collections.deque when you need plain, fast queues or stacks in a single thread. Use queue.Queue when you need thread safety, blocking, or max size — it's built for multi-threaded producer-consumer patterns.
Production Insight
queue.Queue handles thread synchronisation internally — no need for locks.
Without it, you'd need to wrap deque with threading.Lock() and manage blocking logic.
Rule: for multi-threaded work queues, reach for queue.Queue before writing your own.
Key Takeaway
Python's standard library already ships production-ready stacks and queues.
deque for single-thread performance.
queue.Queue for multi-thread safety.
Don't reinvent — but understand the underlying structure.
● Production incidentPOST-MORTEMseverity: high
Queue Slowdown Took Down Support System
Symptom
The support dashboard froze when processing more than 50,000 tickets. Response times for dequeue operations increased from milliseconds to several seconds as the queue grew.
Assumption
The developer assumed list.pop(0) was O(1) like insertion at the end, and that Python might optimise it under the hood.
Root cause
list.pop(0) is O(n) — each dequeue shifts every remaining element left in memory. At 100,000 items, a single pop(0) requires 100,000 memory operations. Over thousands of dequeues, this becomes catastrophic.
Fix
Replaced the plain list with collections.deque and used deque.popleft() for dequeue, which is O(1). Also set a maximum queue size to prevent unbounded growth.
Key lesson
Never assume a standard library operation is O(1) — check the documentation.
If you need FIFO order and performance matters, import deque first.
Always benchmark operations on expected dataset sizes before going to production.
Production debug guideSymptom → action mapping for queue slowdowns and stack misbehaviour3 entries
Symptom · 01
Queue dequeue operation becomes noticeably slower as the queue grows
→
Fix
Benchmark pop(0) vs deque.popleft() using time.perf_counter(). If the ratio exceeds 10x on a list of 10,000 items, switch to deque.
Symptom · 02
Stack returns items in the wrong order (FIFO instead of LIFO)
→
Fix
Check the push/pop implementation — ensure you use list.append() and list.pop() (no index). If you see insert(0) or pop(0), those are queue operations.
Symptom · 03
IndexError: pop from empty list with no helpful message
→
Fix
Wrap the list in a class with an is_empty() guard and raise a descriptive exception (e.g., 'Cannot pop from empty stack').
★ Quick Debug: Queue Performance BottleneckUse these steps when your queue-based application slows down or freezes under load.
Application freezes during batch processing of thousands of items−
Immediate action
Check whether you are using list.pop(0) in a loop — that's the usual suspect.
Commands
time.perf_counter() to measure dequeue time for a single call
print(len(queue)) to check queue size at the time of slowdown
Fix now
Replace list with collections.deque and use popleft() instead of pop(0). Then add a size limit to prevent unbounded growth.
Support tickets processed out of order (FIFO violation)+
Immediate action
Inspect the enqueue/dequeue pair: enqueue should be list.append() or deque.append(), dequeue should be list.pop(0) or deque.popleft().
Commands
print(queue) to see if items are added to the correct end
Check for any insert(0) or pop() calls that mix ends
Fix now
Standardise: enqueue always adds to the end, dequeue always removes from the front. Use deque to avoid confusion.
Feature / Aspect
Stack (LIFO)
Queue (FIFO)
Order principle
Last In, First Out
First In, First Out
Add operation name
push — append() → O(1)
enqueue — append() → O(1)
Remove operation name
pop — list.pop() → O(1)
dequeue — list.pop(0) → O(n) ⚠️
Which end is active?
Only the right/top end
Add to right, remove from left
Best Python implementation
list (built-in)
collections.deque (standard lib)
Typical use cases
Undo, call stack, DFS, parsers
Task queues, BFS, scheduling
Peek operation cost
O(1) — list[-1]
O(1) — list[0]
Risk with plain list
None — both ops are O(1)
pop(0) is O(n) — use deque instead
Real-world analogy
Stack of plates
Coffee shop line
Key takeaways
1
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.
2
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.
3
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).
4
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.
5
Python's standard library provides both
deque for simple single-threaded queues and stacks, and queue.Queue for thread-safe production patterns.
Common mistakes to avoid
3 patterns
×
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.
×
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.
×
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 PREP · PRACTICE MODE
Interview Questions on This Topic
Q01SENIOR
What is the time complexity of enqueue and dequeue when you implement a ...
Q02SENIOR
Can you implement a Stack that supports push, pop, peek, and a get_minim...
Q03SENIOR
You have a Stack. Using only push and pop operations on that Stack (no e...
Q01 of 03SENIOR
What 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?
ANSWER
Enqueue (append) is O(1). Dequeue (pop(0)) is O(n) — every remaining element shifts left in memory. To fix it, use collections.deque which gives O(1) popleft(). For production, always start with deque.
Q02 of 03SENIOR
Can you implement a Stack that supports push, pop, peek, and a get_minimum() operation — all in O(1) time?
ANSWER
Use two stacks: the main stack for all elements, and a 'min stack' that stores the current minimum. On push: compare the new value to the top of the min stack; push the smaller onto the min stack. On pop: pop both stacks. On get_min: peek the min stack. Each operation stays O(1).
Q03 of 03SENIOR
You 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?
ANSWER
Use recursion: pop the top element, recursively reverse the remaining stack, then insert the popped element at the bottom using a helper that pushes elements to the bottom. Alternatively, use a second temporary stack: pop everything onto it, then push back. Both methods preserve LIFO only.
01
What 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?
SENIOR
02
Can you implement a Stack that supports push, pop, peek, and a get_minimum() operation — all in O(1) time?
SENIOR
03
You 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?
SENIOR
FAQ · 4 QUESTIONS
Frequently Asked Questions
01
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.
Was this helpful?
02
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.
Was this helpful?
03
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.
Was this helpful?
04
When should I use queue.Queue instead of collections.deque?
Use queue.Queue when you need thread safety, blocking operations, or a maximum size. It's built for multi-threaded producer-consumer patterns. Use collections.deque for single-threaded or non-blocking scenarios where you need fast O(1) operations.