FAQ: Stacks: Conceptual - Stacks Implementation


This community-built FAQ covers the “Stacks Implementation” exercise from the lesson “Stacks: Conceptual”.

Paths and Courses
This exercise can be found in the following Codecademy content:

Computer Science

Linear Data Structures

FAQs on the exercise Stacks Implementation

There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply (reply) below.

If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.

Join the Discussion. Help a fellow learner on their journey.

Ask or answer a question about this exercise by clicking reply (reply) below!

Agree with a comment or answer? Like (like) to up-vote the contribution!

Need broader help or resources? Head here.

Looking for motivation to keep learning? Join our wider discussions.

Learn more about how to use this guide.

Found a bug? Report it!

Have a question about your account or billing? Reach out to our customer support team!

None of the above? Find out where to ask other questions here!



I was pondering over the question asked: “Why would a Stack be implemented using a Linked List rather than an Array or List?”.

And in Python, it seems to me that it shouldn’t. The list object in Python can already behave as a stack in an optimized fashion, so I don’t know why we would use a linked list which requires creating new objects and methods to do the same task.

It’s also what you find in the Python documentation:


So except for cases where you want a specific kind of stack, I don’t know why we would use a linked list for our stack, am I missing something?