# embedding_metadata

key: chroma:document
string_value:
it in variable so that if I need it later then I can call it with the help of variable but if I don't need it then I said make it from all three convert it to title and return it it doesn't matter on any answer it just doesn't matter that value is no longer with me in variable inside the class I cannot use this name created anywhere again because I have not stored it inside the variable if I need the full name again somewhere then I will have to create it again because I have not stored it okay


key: chroma:document
string_value:
create it again because I have not stored it okay now quickly moving forward this setting a default value as an attribute inside the function I had read default value if someone does not send then that default value is used inside the function everybody remembers this who doesn't remember and if they remember then why don't they raise their hand and who doesn't know about default value from behind what is your name we doubt remember the name ok default Seeing what the value would be, I said


key: chroma:document
string_value:
ok default Seeing what the value would be, I said make a function of D, it has A and B and what should I do, return APS B, okay, I called D and I said P do two, he gave the answer, okay if I don't give P, an error will come, but if I keep the default value of A as zero and the default value of B is zero, now if I don't give my value from here, then which one will be used, zero zero will be used, if I am saying no, then give the value of A, if no one gives the value of B, then take zero, so now


key: chroma:document
string_value:
one gives the value of B, then take zero, so now if I give the value of A as 100, then what will be the answer, 100 P 0, so what is this, the value of C default value came inside print, we opened the function and saw what is the default value of separator, what is written in space and P default, this default value is already written, if I provide the separator myself, then this one will not be used, rather the one that I will give will be used, okay this is what we have default value A here,


key: chroma:document
string_value:
okay this is what we have default value A here, now as I say, said make model what will happen if someone does not supply earBut if he is supplying then 16 but what will happen if he does not supply it brother 2024 this is the default value right whatever you give will get priority first I have given 2025 so if you supply 20 then that will be used okay it's done now what are we saying that setting a default value of for an attribute give the same value we took the same code okay and what did we


key: chroma:document
string_value:
value we took the same code okay and what did we do brother after copying it was okay I indented it then indented it then indented it get descriptive name it is saying old one take the old code okay okay then read odometer intented it then we created this object created an object printed it control x created another object printed it or made another call okay look now just understand [music] here we created a self done odometer variable and inside that what value did we assign it zero set it


key: chroma:document
string_value:
that what value did we assign it zero set it okay what value did it become its odometer did not take here we asked for odometer reading from the user okay what should be taken user is creating an object new car cut Tell him what should the meter reading be, because when a new object is created, what would be its reading, that's why we took it here, so that there is no demand from the user that if I write it here, then it will become mandatory for the user, it's fine, and then I will put zero in


key: chroma:document
string_value:
the user, it's fine, and then I will put zero in it, so if the user doesn't pay, then it will be zero, but if the user pays more, then the meter reading on the new vehicle would be 500 kilometers, which should not happen, it will be like this, that's why I have kept it here, not here, understand again what I am saying, if I say that the auto meter reading is zero by default, okay, the default will be zero, remove it from here, okay, from here, whatever reading comes, take it, if someone doesn't


key: chroma:document
string_value:
reading comes, take it, if someone doesn't pay, it will give zero, but the problem will come when someone pays, brother, what should be the meter reading for a new vehicle, if someone puts 1000, then what will you do, it will be assigned zero, that's why we are not asking him that brother, don't give it, we know that the meter is zero, so it will remain zero, like this What have we done? We have assigned a value of zero. What is this? We have assigned a default value.Aboot has three or three


key: chroma:document
string_value:
assigned a default value.Aboot has three or three when listen brother this question is absolutely correct when this object is created he will run to whom he will run for treatment and what will happen with this how many values ​​are coming from y three values ​​are coming so you are also happy now below here I am explaining the same thing we are giving value to it from our side okay here I will do more and more here brother who will be the self dot owner I said by default owner will come no


key: chroma:document
string_value:
dot owner I said by default owner will come no problem this does not cause any problem to the user the laser is saying that this value here this last one value will have to be provided okay where at y leave it blank leave it blank right now it is common sense it will go wrong leave it like this it is asking for y value assign from y so it is by default so we do not need it okay we did get descriptive name it came to us now what am I saying that brother tell me the odometer reading the car has


key: chroma:document
string_value:
brother tell me the odometer reading the car has run zero miles how many miles has run zero miles here called the function of read odometer it told how many miles the car has run Miles have been driven, you format it as it is with F, then you don't have to do all this, no method, no, the class is created once, whatever objects you create, if you add new things to the class, then you don't have to create the object again, the old ones will be available to it, that's it, okay, I understood, we


key: chroma:document
string_value:
to it, that's it, okay, I understood, we called read odo meter, from here read the odometer of the new car, what is the reading, brother, just check it, I said sir zero mile, let's go, yes meter, okay, now some more things will be added inside it, see what did you do, modifying an odometer value, what should we do, modify the odometer, yesterday I taught you we can do it in two ways, we can modify it directly or do it through the method by doing incapsulation, so when we have to modify the


key: chroma:document
string_value:
incapsulation, so when we have to modify the odometer, it says modifying an odometer directly, you have learned this, rather learn both the methods, if we have to modify the odometer directly, then what will we do, we will say simple, understand brother, what will we say, first of all, take the reading of my new car's odometer and put the reading in it, this will update it It will go but it is a dangerous thing ok and when I read it then instead of zero how much will come 23 will come clear


key: chroma:document
string_value:
of zero how much will come 23 will come clear simple diaryrect we have done the second method which is the value throw method, brother I should make a method not directly, I should not do it, I should make any getter setter, what should I do, I should put in encapsulation, okay so what will we do now take our same class and inside it I will copy the whole class and bring it down, inside it I will make a method, instead of read odometer, what will be its name, set odometer this has become get


key: chroma:document
string_value:
be its name, set odometer this has become get odometer this is which is bringing the reading, it is getting the value and what will be set odometer self when it sets it, it will also ask for the new value, right, new reading, now what can I do in the new reading, some smart person should come, like people do, they get the meter of their motorcycle reversed, the gas is running low, the car has run 5000 kilometers, I have gone to the mechanic, I am going to sell it, it will cost a lot of money,


key: chroma:document
string_value:
am going to sell it, it will cost a lot of money, the new reading of the meter, how much is 1000, it happens like this, so what are we going to do, if what is the new reading, less than which self dot zero not the old reading, if what is the new reading, I am putting less If the person is taking old readings then what will we call him, he is not becoming a cheater, he is not doing ding with us and if it is not so then what should I do brother, put which ding in self dot odometer reading, okay,


key: chroma:document
string_value:
which ding in self dot odometer reading, okay, now it will come through the method, it has become set odometer, change it and get it back, similarly the read is also doing the same thing, no matter what the name is, but the fanty is getting set, so I set the gate, now this is done with me, now let's create the object again, we created the object again, g odometer, okay, if someone enters it, then he will say brother this will not be made, I will keep telling you now, then it will be understood,


key: chroma:document
string_value:
keep telling you now, then it will be understood, get descriptive name, okay now I said my new car, my new car, please gate it, what will you gate it, how much will the odometer come, zero, okay, now it happened that my new car ran 10 kilometers, okay, so what will I say brother, increase the reading and put how much in the set odo meter, put 10 kilometers, he put it, now I say my new car, please gate it again and tell me how much reading is coming, how much will it show, brother it will show


key: chroma:document
string_value:
how much will it show, brother it will show 10, now I I came again and said my new car dot should be reset again and the meter reading was 5 kms and now the car has driven 10 kmsSo even if it goes in reverse it will not be five it will be 15 only now if someone puts less in it then it will not let you put in it rather what will it say it will not happen like this it will not happen now the understanding is changing my son I am also saying that if the new reading is less than the old reading now


key: chroma:document
string_value:
the new reading is less than the old reading now what is the old reading now what is the new reading pa listen to me what is the new reading pa now tell me tell me yesterday you saw on the meter it was 10 kilometers okay always you brought it in the car now will there be five reading on the meter will it be beyond 10 [music] no it cannot be five so if someone tries to make it five then what will we say son take it forward ahead okay so that's why now when I put it here what does it say brother


key: chroma:document
string_value:
now when I put it here what does it say brother okay sir I don't remember an hour ago so what should I hide talking about yesterday hide it it will come its turn will come just now it has not come here I understood that thing okay well now go back to modify get set we had read it earlier okay this has come update autometer this is what it has written if the mileage is more than the old one then will give you can roll back okay the method increment ordo pea inheritance inheritance inheritance


key: chroma:document
string_value:
ordo pea inheritance inheritance inheritance this we have it now here we have created a class which class have we created electric car okay we have created this class electric and from which car it is inheriting from car ok listen to this carefully don't talk ok why did we inherit electric car won't all those things be there which are inside it ok let me change the question I am saying this brother there is a tree okay and there is a neem tree is it not a tree can I say this brother name tree


key: chroma:document
string_value:
is it not a tree can I say this brother name tree it's tree okay can I call it this electric car it can I say this chair is a furniture furniture doesn't come okay can I say that the shirt which is a buckle can can I say projector it's screen okay coming so when you have inheritance relationship and it should be in relationship okay now You will say dog ​​human be dog human if it is done the other way round then it is also ok, some property gets acquired [music] but when we are writinIf we look


key: chroma:document
string_value:
acquired [music] but when we are writinIf we look at the relationship, should I easily connect it or not? Why, if I connect an electric car to a neem tree, will it refuse me? No, I will not refuse you. You don't have to use syntax for this class of electric car. Okay, but you will use your common sense, brother, my purpose of doing this was that I could connect the old written code to my function. So, are there such functions in the neem tree that will be useful in the electric car? If I


key: chroma:document
string_value:
that will be useful in the electric car? If I connect them, even if I connect them, they will remain virtually useless for me and I will not be able to utilize them. Okay, but the functions of the class of a human being will definitely be inside a student. He is a human being, he eats, drinks, sleeps, dies, wakes up. Okay, yes, a student is an addition, he takes holidays, comes late, pays fees, fails in exams, these are additional properties of the student. [Music] No, but he needs human


key: chroma:document
string_value:
of the student. [Music] No, but he needs human properties, doesn't it mean this inheritance? Okay, there must be some, it should be there. We will connect it. We will not connect it. If this If there is a relationship, then we should mark that class. Okay, so now I am also saying that electric car is a car. Okay, but along with that, the car is also a car, so there will be some problems, right? If it runs, it will not run, it will not run, so we have marked the car inside the electric car.


key: chroma:document
string_value:
we have marked the car inside the electric car. Okay, we have created this electric car. What is the make of the electric car? What is the electric car demanding from us? It will have its make, model, year, and it can also demand some other things, like, what is its price? How many amperes of battery is installed in it? Okay, and that's it. Let's give the price and battery, that's enough. Okay, now look here, we have used one. What is super? Super is at the top. Super bucket is at the top. Why


key: chroma:document
string_value:
is at the top. Super bucket is at the top. Why have we used it? Look, what object am I creating here? Please understand what object am I creating with the help of the app. Okay, like I will cut the object, it will run to its class, it will be like this. It came to it. It said, what is your make? What is the model of Tesla? Your model S is which year was it made? How much is your battery worth in 2024? How much did you spend? How much did you spend?What happens next when these things reach here,


key: chroma:document
string_value:
happens next when these things reach here, then what does our class do inside the variable, it assigns all these things, it gets them assigned like this, but now how bad would I feel if I start assigning them here, said make, make, dot model, model and self, year, year, dot price, price, dot battery, okay, I got all of them assigned, when I had to get all these signs done myself, then what was the need for this, washing clothes, making breakfast, what was the need for getting married, earlier


key: chroma:document
string_value:
what was the need for getting married, earlier we used to use one pair, now we have to do two, what was the need, he said brother, no I am not doing it, the iron got down, here what did I say, hey brother, you can do it, come now what did I say, brother, I have brought you here for rest, so do whatever you can do, what can you do because what all things are present with it, a model year and odometer will come to it, whatever you can do, you have the ability, do that, the rest whatever work you


key: chroma:document
string_value:
the ability, do that, the rest whatever work you cannot do, I will do it myself, okay, do the rest of the work, so from here we started I diverted it towards the super class that whatever work this super class can do, it should do it and I am just telling you to explain that I have sent it there and there is no need to send it, I have come to your house, okay, virtually here, okay, I am telling you to explain that after taking this much stuff, I will send it after that, go and do it, make the


key: chroma:document
string_value:
I will send it after that, go and do it, make the ability with you, the rest I will do it here, but it is fun, so in this way, I was saved from setting the three parameters, okay plus now I have come, now give me the description of the electric car, okay, what was the function on this, get descriptive name, good, should I make it again, so why did I bring it, you already have the ability, that function is already made, that function is already made and this is also available, brother, now I do


key: chroma:document
string_value:
and this is also available, brother, now I do not need to make it again, then in the same way, which ones are there, brother, set autometer, get autometer, this is already available to me for electric car, let's see, let's see, I made this, my electric car descriptive name, this I have not created the function for descriptive name here but you will see that my Tesla has a descriptive nameThere is also the name of the autometer, there is also the make, model, price, there is also the set


key: chroma:document
string_value:
the make, model, price, there is also the set odometer, from where did I bring it in the code, okay, it has come through inheritance, so now I have to repeat all those things, if I have to write any further text, you write that here, there is no need to repeat that work, okay, did you understand this, here if I say get odometer, then how much will Tesla get, zero, which car's Tesla is coming, Tesla's, okay, there is no problem in understanding this, okay, let me first try to understand the


key: chroma:document
string_value:
this, okay, let me first try to understand the question, what have you defined twice, the make, model, which is it, you must have defined it here or you defined it in Tesla, in Tesla you are saying that I should also do super, if you have created different cars, have you created all the cars, you have created only the car, so understand this, I have a car class, okay, what do I have from the car class, two cars were made, which ones? Brother, who made one car, Honda [Music] and one car Which


key: chroma:document
string_value:
who made one car, Honda [Music] and one car Which Suzuki did you take? Okay, now I have this class divided by two different classes. Okay, maybe now I am going to make an electric car. To make an electric car, I can also do this that I make an electric car here and also divide it. Okay, I am not doing this. If for example, I am doing this that I am connecting the electric car with the Suzuki car. With whom am I connecting Suzuki. Now tell me whose properties will it have? The properties of the


key: chroma:document
string_value:
properties will it have? The properties of the car and the car. Okay, it will have its own properties. Will its own properties come in the electric car or not? So, that is why the electric car, the car which has inheritance classes standing with it, none of its properties will come in it. So even if it is divided five times, the back model is different, it does not have any reach there, its reach is only towards its parent. Okay brother, so okay, I understood this thing, I understood super


key: chroma:document
string_value:
okay, I understood this thing, I understood super well, where does this super take you [Music] Yes, so that direct electric car What a thing, it comes on time. Hey, I am just saying this to explain. Maybe Suzuki has brought out something like this, Tesla orPeople liked the tired engine body tired if there is a slight bump then just the child should sit, the body should sit, the tail one will make a tired like this we will take some features from here, right, so to explain that, to make a


key: chroma:document
string_value:
from here, right, so to explain that, to make a sequence yes, okay, okay, this is a childhood question that you have asked in 55, if we read from the beginning, if a variable will be created again, then the old one will be overridden, when you define the car class again, then the code from the old one will be written from the memory, but the new car will be in the memory, this is what we did now, but this car that I have created above, I also created a class car, it did not have many features,


key: chroma:document
string_value:
a class car, it did not have many features, so now that is gone, now when I execute this one, then when I call here, which one will be there, definitely the latest one that I have executed will be there, ok, let's move forward, defining tribute a method for child class, now there are some attributes for the child class, understand, see what I am doing yes [music] no, understand brother, what are we doing now, I am just removing this from y, I am also removing this for some time, follow the code


key: chroma:document
string_value:
also removing this for some time, follow the code of the back I will go with it, okay, this is also fine, okay, now what am I doing, I am putting a parameter inside the electric car, which parameter? This electric car is redefining the car, here self dot battery battery size electric battery is installed, we have written its size, okay, what is the size of the battery, now I have created a function on this, describe battery of the car, no, which battery, okay, car hangs, battery size kilowatt


key: chroma:document
string_value:
battery, okay, car hangs, battery size kilowatt battery, next I called this, created an object of my Tesla my Tesla, okay, after creating the object, called the function of get descriptive name, what did it say after that, describe the battery, tell me what is the battery, so it says brother 2016 Tesla Model S and there is a 70 kWh battery installed inside the car, okay, we are going towards an important thing, let me see, the book has addressed it, no, overriding method from parent class, now


key: chroma:document
string_value:
it, no, overriding method from parent class, now what happened is that my car is the car class, which is the car class, I should first create a heading, I am not entering the code inside it, otherwise later you They will say, I don't know where you reached from, I will make this heading and get the whole code again.Let me see this heading is done we have an overriding method form pet class my car class whose code I am taking again okay I took its code again I am creating a method inside it


key: chroma:document
string_value:
its code again I am creating a method inside it [music] hmm f gas tank gas tank does not mean a car that runs on CG rather it means gasoline, that is, petrol so the word petrol is not used all over the world they use the word gasoline or gas they use fill gas so I printed car tank bf on this [music] okay now I have printed this car only Tesla has printed it rather it has printed the electric car and then Tesla was made and when Tesla was made then Tesla will get all the things of the car now I


key: chroma:document
string_value:
Tesla will get all the things of the car now I told what do you have my Tesla what do you have so my Tesla said I have the battery size as well describe the battery as well fill the gas tank ok fill the gas tank we got stuck why did we get stuck where did the tank come from in the electric car electric cars do not have a tank okay that means when we call a class That inheritance was in the irritant class, but in a different style, in a different style, I mean, Abba was a very good Balkar, he


key: chroma:document
string_value:
style, I mean, Abba was a very good Balkar, he used to sing melodious songs, he used to give a lot of melodies, what did he do, yes, it was a very melodious Guru, but what happened now, this feature of melodious voice has been written in the child as well, but instead of singing songs, what does the child do, he recites well, recites Naate, recites the slogan Takbir Allah Ak, okay, that feature is available in the child, but with different body, different implementation, what is that feature


key: chroma:document
string_value:
different implementation, what is that feature irritant implementation in the child as well, what is its implementation different, one thing is that what is that implementation, it is different, so we redefine that function, okay, what do we do with the function, what was written in Abba's function, he sings melodious songs, but if that function will run in the child, he will also be singing melodious songs, so what do I have to do, I will have to overwrite this function, I will have to define


key: chroma:document
string_value:
to overwrite this function, I will have to define it again and write there You will have to tell that the child is not singing melodious songs but melodious Nath is okay.The issue is that I will have to define this function of gas fill tank again. What should I do? A fill gas tank. Okay, and here I will say brother there is no gas tank needed in electric car. So now if someone sees the method of gas tank, and even if he drives it, what will happen there? No gas tank needed in electric car. What


key: chroma:document
string_value:
there? No gas tank needed in electric car. What do we call this? Method overriding. Look, there was one thing, method overloading. Listen to me, one thing was method overloading. I created a method called add. I created a method for add, okay, I called it. I again created a method for add, which takes three parameters A, B and C and adds. Okay, now if I call it, which call will happen, the latest one that was run, second first, the latest one that was executed, why would that call be because


key: chroma:document
string_value:
that was executed, why would that call be because when I redefined the old function, then that function got overridden, what happened? It was not overloaded. What happens in overload, both are running. In some programming languages, overloading is going on. This has two parameters and this has three parameters, so these are separated. Okay, what are these counted, they are counted separately, in C-shape, not in Java, even in JavaScript, in Python, overloading does not happen, overloading does


key: chroma:document
string_value:
overloading does not happen, overloading does not happen, it overrides, it overrides, for overloading I had taught arbitrary parameters, no matter how many parameters, this overloading is not allowed, overriding happens, okay what happens, overriding happens, now the scene is that if this overriding is of the method of the parent class and where is it, if it is inside the child class, then this is called polymorphism, what is it called, it is called polymorphism which is our third pillar, if


key: chroma:document
string_value:
called polymorphism which is our third pillar, if you remember, yes, in chemistry also it is poly means many morphisms means many faces, polymorphism is the concept that now we have only one method but it has two implementations, there is only one method but it has two implementations, abba will sing a song with the same method, what will the child do with the same method, what will this be called Polymorphous, you have seen these different behaviors in different places, I have told you about


key: chroma:document
string_value:
in different places, I have told you about the methods, you know, I have read in many places that brother, many timesNow I have already explained how many are there in 1 and 2. This plus is also a polymorphic behavior. If it is written like this, then it means that if it is getting integers, then it is doing the sum and if it is getting strings, then it is cutting the cone. It is a single operator behaving in two different styles. It is a single face but what is its function and what is it, it


key: chroma:document
string_value:
face but what is its function and what is it, it is two. So this is also polymorphic. [Music] Hello, it calculated the length of a string. And what should I do here, should I find out the length of a list? This time, I found out the length of a list. So what is the method of length also happening? We have many such methods which are behaving polymorphically. So now what concept do we get here that the gas tank must be getting filled inside the car, but inside the child, there is another


key: chroma:document
string_value:
the car, but inside the child, there is another behavior of the same function. It does not need gas. So one function has been performed twice, of the same name. And the behavior is different both the times, that is, if a car calls it, then its behavior will be different and if a Tesla calls it, then its behavior will be different. Now that you are understanding the point, you have understood inheritance, encapsulation and to some extent you have understood polymorphism as well. Polymorphism


key: chroma:document
string_value:
understood polymorphism as well. Polymorphism doesn't only happen in methods, there are also three or four other ways in which polymorphism is implemented, but right now we have a short time, we won't go into so much detail, otherwise there are duck typing and many other concepts that we can do, but this is enough that you are able to understand that friend, this is polymorphic behavior. The fourth pillar is what? Abstraction doesn't exist in Python. Abstraction is a very powerful concept, but


key: chroma:document
string_value:
Abstraction is a very powerful concept, but this concept doesn't exist in Python. But what did they say? Someone just added it in the same way, someone created a separate module. I have published that if anyone wants to use abstraction in Python then they can take our services, import ABC, what is ABC, abstract based classes, don't worry right now, we are not reading it, it's okay, now let's come to the main idea first.Let's focus on this, we are not touching this advanced level topic right


key: chroma:document
string_value:
are not touching this advanced level topic right now, I understood that when I have created a class, then now all its things are coming to me, now I am not doing this, everything, property, props is coming, all the things are coming, so now if I see that brother, okay, it has come, I have benefited from it, but this is useless for me and if someone uses it because of me, then a strange output will come, so what do I do in his implementation, change it, guide him, tell him, okay, an important


key: chroma:document
string_value:
it, guide him, tell him, okay, an important concept we have to do is not an object as an instance, what is the object as an attribute, what is this that I have, a [music] abutting type, this is also what is it, okay now what I am doing is an element and this is an integer, we have also read that all these are objects, what are all these, objects are like this, right, what we are creating, is that not an object, this is also an object, so can I put this object as an attribute I am, that is why I


key: chroma:document
string_value:
this object as an attribute I am, that is why I am studying the topic, object as an object, basically the object that is used is itself an object, so object as an object was made and is being used directly, now what will we do with our created object as an object, the only question is why, why, look, so look at ours, let's go brother and go to offer namaz, well done, run quickly and we will come back, you guys, okay, what was our topic, good, what happens in object as an object, that when we


key: chroma:document
string_value:
what happens in object as an object, that when we have a class, then let's study it in the next class, friend.


