Python Namespaces

In this tutorial I look at how Python organizes it objects in Namespaces. In other words we are looking under the hood of Python to see the systems that helps avoid name conflicts.

[stevenewbank]

I appreciate the time you must spend in making your videos, I'm making my way through all of them. I love your teaching style of continuous reinforcement; tell them, tell them what you told them, and tell them again...and when you next see them, tell them yet again. Best way to teach in my opinion; for me, certainly the best way to learn. Thanks again.

[fadilyassin]

your contribution to teaching python is excellent

[SusanAmberBruce]

I hope your next video explains how to find and look at namespaces.

[arnoldjuliusmpofu]

Much appreciated. Very clear. However no clear explanation on different namespaces

[martinkaspar]

hello dear John - overwhelming tutorial - very helpful. One question though can you put togehter the most important infos into a cheatsheet - a Summarizing Cheat Sheet to download would be fantastic.


above all - keep up the great work. It rocks!

[solopython]

Can you tell me which tool you used to make the presentation?

[joeking]

So 'name' would have done or 'nameobject', so where / what is the 'space' name/value pairs yep ok name/object pairs great what is NAMESPACE and where is it why does it even have to be mentioned, it's obvious that ANY programming language has to have a unique name to refer to anything, I would guess that even a beginner would totally see that if they say x = 7 and then x = 8 that they now can't access the 7, so surely that is 'implied' with ANY language that you have to use unique variable/object etc etc names to keep thing isolated, so what is the deal with what/where/how this is used / needed / needed, when writing a python program where do you type namespace if you declare a var z = 9, than z is stored ( i guess like you say in virtual dictionary somewhere ) and the programmer moves on, so why do those people creating this cryptic language bother to expose the total confusion that this brings when you don't actually use it, or do you, if how/where/when/why as every var you create HAS to be a different name that goes without saying, but as a the boffin language writers always seem to do do, if you make something complicated then why not, it makes us look like we are really thinking really deeply, why make it obvious if you don't need to, I think that defines python from what I am seeing so far in my quest to get some existing code ported. And from what I see looking out there there I feel an awful lot of folk that 'think' the have 'got it' but when put on the spot they may fumble, just like me.
So in summery What Where is namespace I get name but I dot get space but your nameobject may have been the better implementation of it.
I'll give another example of this idiotic invention, 'self' totally useless and could have been left out as that is also 'implied' from what is calling the called object knows who's calling and python i am reliably informed passes the caller automatically so WHY OH WHY do you need to use 'self' in this so called beginners easy to learn modern language, please don't think I am being in any way critical of yourself, thank you for trying to explain something that the writers of the language should have never have mad so damned cryptic to begin with. Many thks, and would most grateful to be put straight in the understanding of this weird language.