split() returns substrings, not integers. So if you do a,b,c = '4 5 6'.split(), a will be a string '4', b will be a string '5', and c '6'. Then if you 'add' a and b, they will be concatenated as '45'
Absolutely, I have noticed too that he made a mistake. Split() is a string method and it returns a list of substrings. So each value will have to be of the string class and not of the int class.
When you are using **kwargs for a parameter, you are telling it that what you are giving it is going to be packed into a dictionary. It's not expecting a dictionary, it's expecting keys and values with which it will create a dictionary. So, the reason it doesn't work is that isn't what is being expected. However, you CAN use the dictionary syntax, if you the ** operator to unpack a dictionary into names and values, which then would be repacked in the function. The following is legal syntax: func(**{'a':100, 'b':100})
you will not be able to do calculate on split return elements , because it returns strings "sub_strings" . do type(a or b or c ) . do int(a or b or c ) first , man focus . good job .
@@oggiai I hate to be the bearer of bad news , but, Python is almost as idiosyncratic and weird as Perl is. I think I'll stick to C/C++ , at least it makes sense consistently !
it's just for passing an unknown number of key-value pairs to a function. There are other ways to do that (simply passing a dict), so I agree **kwargs is not extremely useful. But as a programmer you often need to figure out how other peoples' code works, so you should learn these nuances of the language.
There are many uses, but one of the most common is simply if you want to have lots of options when calling a function but you don't want to have make a big long list of function parameters for all possible options, especially when most of the time you only need a small number of required parameters. For example, if you have a function that sorts list, you could have additional options such as whether you want it in reverse sorted, or just the first n values, or some other feature. You could make those additional options supported by **kwargs. If you don't need them, they can be left out entirely. If you don't include them in the function call, it doesn't throw an error and just makes a zero length dictionary. When you do want those additional options, just include the ones you want.
and I have to add, I strongly disagree about it being "not extremely useful". A lot of the built in functions of Python use this very feature. And understanding it isn't just for understanding other people's code, but for understanding a lot of the official documentation. I for one have written a lot of pieces of code that were a bit dodgy with additional arguments that were only needed in some special cases that I later realized, "I should have just used **kwargs for that".
@@flioink Yes, it does require a bit of additional work when creating the function, but it provides you with more flexibility when calling it. Another common use-case for it is if you are creating a command line programs. A typical command line program often has standard use cases that involve a small number of options, but has large numbers of optional options and parameters that can be used. If you ever use command line programs then you should be very familiar with the pattern, and this is how you can implement it.
![“อ.เบียร์ คนตื่นธรรม” มาตามคำเรียกร้อง แหกศาสตร์ฮวงจุ้ย เตือนสติอย่างมงาย | แฉ 7 พ.ย. 67 [1/3]](http://i.ytimg.com/vi/5fc4S3xBNfc/mqdefault.jpg)
split() returns substrings, not integers. So if you do a,b,c = '4 5 6'.split(), a will be a string '4', b will be a string '5', and c '6'. Then if you 'add' a and b, they will be concatenated as '45'
Absolutely, I have noticed too that he made a mistake. Split() is a string method and it returns a list of substrings. So each value will have to be of the string class and not of the int class.
Thanks for the tutorial, i like how you went through examples while you explained it. Not many people do that
May god bless your soul i was looking everywhere for a basic explanation and i found your channel.
Great work, simple and very helpful. Thank you
Very well explained! Thanks
I love that mGaetz falls into the same category as Betamax.
Matt Gaetz = loser. That's great
Thank you for your videos! If there's the option, I always choose to see your explanation
Wooow - **Great** teacher! 👍
That was explained wonderfully, thank you!
@4:58 Thanks for the details about this!
Great job explaining this! Thank you!
Very useful tutorial on the topic and very sharp. Thanks.
Great tutorial sir!!
عاشت ايدك يا سبع كلش افتهمت اني 😍😘❤
Great sharing, Sir!
a,b,c='4 5 6'.split() # a, b and c will be type str not integer
Yes I may have a mistake in my video- it doesn’t automatically cast it to an int.
@@oggiai yes but overall your video is great
Thank you so much!!!
Thank you Sir.
Wow this was great. Thank you!
thank u uncle i was looking for my board exams
Super clear
اشهد ان لا اله الا الله اشهد ان محمد رسول لله
do we know why when packing a dict with **kwargs that you cant use the standard dictionary syntax (a:100,b:200). Great video btw thanks
When you are using **kwargs for a parameter, you are telling it that what you are giving it is going to be packed into a dictionary. It's not expecting a dictionary, it's expecting keys and values with which it will create a dictionary. So, the reason it doesn't work is that isn't what is being expected.
However, you CAN use the dictionary syntax, if you the ** operator to unpack a dictionary into names and values, which then would be repacked in the function.
The following is legal syntax:
func(**{'a':100, 'b':100})
Great insights and explanation. losers['c'] makes so much sense in that particular category! cheers
you will not be able to do calculate on split return elements , because it returns strings "sub_strings" .
do type(a or b or c ) .
do int(a or b or c ) first , man focus .
good job .
Not exactly what I'd call packing and unpacking but hey , It's only Python so no harm done I guess
That’s what Python calls packing and unpacking. And it’s useful to know
@@oggiai I hate to be the bearer of bad news , but, Python is almost as idiosyncratic and weird as Perl is. I think I'll stick to C/C++ , at least it makes sense consistently !
still don't get the point of **kwargs or why it's useful
it's just for passing an unknown number of key-value pairs to a function. There are other ways to do that (simply passing a dict), so I agree **kwargs is not extremely useful. But as a programmer you often need to figure out how other peoples' code works, so you should learn these nuances of the language.
There are many uses, but one of the most common is simply if you want to have lots of options when calling a function but you don't want to have make a big long list of function parameters for all possible options, especially when most of the time you only need a small number of required parameters.
For example, if you have a function that sorts list, you could have additional options such as whether you want it in reverse sorted, or just the first n values, or some other feature. You could make those additional options supported by **kwargs. If you don't need them, they can be left out entirely. If you don't include them in the function call, it doesn't throw an error and just makes a zero length dictionary. When you do want those additional options, just include the ones you want.
and I have to add, I strongly disagree about it being "not extremely useful". A lot of the built in functions of Python use this very feature. And understanding it isn't just for understanding other people's code, but for understanding a lot of the official documentation.
I for one have written a lot of pieces of code that were a bit dodgy with additional arguments that were only needed in some special cases that I later realized, "I should have just used **kwargs for that".
@@claffert Ok, but then your function has to check if those additional are present, no?
@@flioink Yes, it does require a bit of additional work when creating the function, but it provides you with more flexibility when calling it.
Another common use-case for it is if you are creating a command line programs.
A typical command line program often has standard use cases that involve a small number of options, but has large numbers of optional options and parameters that can be used.
If you ever use command line programs then you should be very familiar with the pattern, and this is how you can implement it.
So why is mGaetz a loser?