Correction :- Both stack memory and heap memory allocated at runtime by interpreter. First stack memory is allocated and then heap memory. Just ignore when I say stack memory is allocated by compiler. I was telling the wroking of other language...it's not true for python. Everything is correct in abkve video except when is say stack memory is allocated by compiler.Please let me know if any questions...
hey bro, i just wanna say that you are awesome, the way you explain in very simple words as much as you could is also wonderful, thank you for and its totally appreciable.
Hey, great video! Particularly, I like how clear and detailed your explanations are as well as the depth of knowledge you have surrounding Python. Since I run a tech education channel as well, I love to see fellow content creators sharing, educating, and inspiring a large global audience. Keep up the great work!
Bro you are wrong both memory created at run time because python is dynamic semantic type language so during run time both memory created to store the variable name and it's data reference in heap and inside interpreter environment there is no compiler its an compiling process that's is part of interpreter that is referred to bytecode generator dude
Hey you explained programming very well ,but definition is also important right say that too (example shallow copy and deep copy) we want definition also please you do.
Isn’t Stack data structure follows FILO? In your example while storing references seems like it follows FIFO. I think it should be FILO num1-> num2-> add(x,y) Could you pls help?
Two things here, variables are references for objects or values that you create in python. Second thing is, variables are names and internally memory is allocated for variable names. It means variables names are also values. Hence, I said that statement
@@Codeyug ok buddy but i heard people say that references/alias have the same memory address as the objects imean (&reference variable) will be same as (&object) right so how come object is in heap and reference variable is in stack .could u comment on that
Correction :- Both stack memory and heap memory allocated at runtime by interpreter. First stack memory is allocated and then heap memory. Just ignore when I say stack memory is allocated by compiler. I was telling the wroking of other language...it's not true for python. Everything is correct in abkve video except when is say stack memory is allocated by compiler.Please let me know if any questions...
hey bro, i just wanna say that you are awesome, the way you explain in very simple words as much as you could is also wonderful, thank you for and its totally appreciable.
thank you so much...we are wating for this...
Thank you.. Keep watching
Great... Eagerly waiting for your video..plz send me python notes..
Good brother nice explanation
Hey, great video! Particularly, I like how clear and detailed your explanations are as well as the depth of knowledge you have surrounding Python. Since I run a tech education channel as well, I love to see fellow content creators sharing, educating, and inspiring a large global audience. Keep up the great work!
Thank you so much.. All the best for your channel.
@@Codeyug Hey bro where did you learn this from? Do you recommend any books or anything?
Nicely explained!
Bro you are wrong both memory created at run time because python is dynamic semantic type language so during run time both memory created to store the variable name and it's data reference in heap and inside interpreter environment there is no compiler its an compiling process that's is part of interpreter that is referred to bytecode generator dude
grt explanation
Thanks..
Hey you explained programming very well ,but definition is also important right say that too (example shallow copy and deep copy) we want definition also please you do.
Okay.. So I think learners will note down what I say. But, I will include definitions on ppt from next time.
I want the definition bro ,I am your subscriber ever and forever.
@@kittureddy9297 okay and thanks. .. Next time i will take care of that.
You should not be thanking you,we should be thanking you.
Isn’t Stack data structure follows FILO? In your example while storing references seems like it follows FIFO. I think it should be FILO num1-> num2-> add(x,y)
Could you pls help?
thank you so much..
Keep watching videos on my channel..
thank you bro
Welcome
Chhota correction, garbage collection works at run time, not at compile time. 6.39 mei
Thanks for correction
Bhai part 3 kaha hai iska
Correction is size of stack is calculated at compile time and assignment happen in interpretation.
Correct me if i am wrong.
all variables are objects in python .What the hell are u saying here
Two things here, variables are references for objects or values that you create in python. Second thing is, variables are names and internally memory is allocated for variable names. It means variables names are also values. Hence, I said that statement
@@Codeyug ok buddy but i heard people say that references/alias have the same memory address as the objects imean (&reference variable) will be same as (&object) right so how come object is in heap and reference variable is in stack .could u comment on that
Why you make english title and speak indian ?
I don't know why this is happening with my videos. Learning Hindi and then python will take lot of efforts..