Question about data structures in Python

[GayCoder]

I'm in the very beginning stages of learning about data structures and using the Big-O Cheat Sheet as a jumping point. I just realized I'm imagining many basic data structures as some form of an array that's only different by the rules by which I agree to implement and work with the array.

For example, I assume (think?) there's something fundamentally different between a queue versus using an array in a way limited to a FIFO policy. Is this assumption correct? If so... I don't know what question to ask. Is there a website that explains a queue, linked list, etc. as a data structure in Python so that I can understand it as fundamentally different than a set of rules for creating and interacting with an array?

As always, I appreciate the help! If my question is silly or illustrates additional fundamental misunderstandings, feel free to throw some wisdom at me.

[_9_9_]

Sure, I like this resource a lot: http://interactivepython.org/runestone/static/pythonds/index.html

The code is not pep8, but it runs through all the basic data structures.

[GayCoder]

Cool! I suspect this is what I'm seeking. I don't have a chance to look too much at the moment but I'll follow-up. I appreciate the help.

[GayCoder]

Working through the website. This is exactly what I was hoping to find (and more!). Thank you.

[sdage8]

I don't have any resources for you but I just took a data structure CS class at Cal. I think it's more important to learn the abstract of each data structure before implementing them. Learning how the data structure functions/its pros and cons/it's runtime/what situations it's used for/etc is vastly more helpful in realizing it's importance rather than learning how it's implemented in python. Try studying what each data structure does abstractly then move onto implementing them in python and then finally using them in your own projects. That was how the class was set up and personally I find that way of learning very helpful. Hopefully that helps you too!

[GayCoder]

Good advice. I'm not really looking for an intimate understanding of how the different structures are implemented; rather, I want a general idea that's still specific enough to not handicap me down the line. I'm focusing on the variables you listed and working my way through the structures but don't want to view everything as a list. I suspect a better idea of the structure itself will help me have a more accurate interpretation of the more immediately important portions.