ALL 11 LIST METHODS IN PYTHON EXPLAINED 

Very true, I often use lambdas in these situations to show that people can really implement their own custom functionality :)

why sadly bro

@@harmly2682they asked for tips at the end of the video, there are no extra tips he could add

I'll look into it!

O(1) is 1 action O(log(n)) is wierd(search up "harvard cs50 phonebook" for example) O(n) is as many actions as iterables O(n²) is garbo Example you want to count from 0 to 10: O(1) = [10] O(log(n)) = [1, 2, 4, 8](10 wouldnt be part of the logarithm) O(n) = [1,2,3,4,5,6,7,8,9,10] O(n²) = [[1,2,3,4,5,6,7,8,9,10]1,[1,2,3,4,5,6,7,8,9,10]2,[1,2,3,4,5,6,7,8,9,10]3,[1,2,3,4,5,6,7,8,9,10]4] ect up to 10

Basiji?

PyCharm

Slicing creates a new list, while most of these methods are performed on the list in place

Correct. Python list sorting methods are stable, meaning that equal keys preserve the original order. The video was incorrect on that point.

It's going to get really confusing for people following the file name dates! Because that's when I created those projects ;)

@@Indently oh alright

I recommend breaking that problem down into smaller problems. It's very unlikely I will make a video so specific to that problem.

its just a little more memory efficient than list = [ ]

@@deei5130 interesting, thanks, I might see what could do for me, I have cases where I cannot avoid lists with 4-5 million elements. Stupid proprietary data environment...

I use lists in a game to create objects from an enemy class. The game runs on a loop and when the player dies, a new game is started and obviously the lists must be reset so that the new game is not already filled with enemies. I use list.clear() for that.

@@TheMongole24 cool, thanks for the explanation!

Clear is better memory wise

@@massy-3961 thanks

i think list.clear() means that list = null; // work garbage collector, clean memory list = [] means that list = new list(); // new pointer in memory

Actually “l.clear()” would be more equivalent to “l[:] = []”

clear empties your existing list object, while = [] creates a new empty list object. If you don't care about the particular object reference value, the differences are negligible in practice.

help*

a.append(argument), you are missing the argument that's to be added to the list, in your case you are not appending anython to the list.

It's just type hinting, it isn't required, lists are the same

Because we are adults now, and Python offers beautiful tools to simulate static type checking :)

I think you meant to paste that on Google search.

@@Indently No. This does not work on all compilers.

Please explain what you mean.

@@Indently He tried your code in an older version of Python and had this error because subscriptable types (like list[str]) have only been added since Python 3.9 (and you can get them with `from __future__ import annotations` if you have Python 3.7 or 3.8). He could use typing.List instead of list or just not write the annotations.

@@lemmenmin7676 Python doesn't have any compilers. Python is interpreted language.

Please be more specific about what you're trying to explain.

@@Indently The class *list* in Python implements what's called arrays in almost every other language and data structures books (more precisely dynamic arrays, C++ call them vectors but that's an horrible choice all of its own). If you're teaching programming with Python, it's a constant pain to every so often catch yourself referring to lists when you meant arrays just because the chosen language didn't use the standard name. Not really important in most other contexts (a rose by any other name…).

@@chaddaifouche536 Your point being?

@@callbettersaul I'm just explaining what maxim was referring to. All in all this video is exploring the list class in Python so I don't think this distinction is very important here but some people more accustomed to other languages do find the name irritating.

Python has an entirely separate “array” module. And then there are NumPy arrays.