I've been blindly pattern matching for spinning up repos for awhile now and it's nice to see explanations for a lot of those choices. I also didn't realize all the pytest functionality I was missing. I like this longer/more detailed style too - it's necessary for training strong engineers. (Though, not sure if it's the best choice for TH-cam growth). Thanks for making this. I'll be recommending it to coworkers.
We'll see how this one performs. I already have a pretty sophisticated audience so maybe they'll love it! If not I'm fine with a video tanking now and again, I know some people will still find it useful. Thanks for watching as always!
@@mCoding man you are the only one with real content, with the aim to teach beyond basics. your structure is awesome. the editing style is top notch. keep it up please. you are great
Utterly brilliant walkthrough! Our company is currently implementing automated testing for a new project and all config requirements have worried me that I have no clue what's going on and would have no clue if stuff went wrong! This is so clearly explained and motivated, I feel perfectly equipped to ensure we can implement it all and know all our tests are run!
TH-cam is my Netflix when it comes to content related to programming, databases and DevOps, so I go through a ton of content regularly. but this video was one of THE most informative pieces of content I've ever watched. As a lower-intermediate Python programmer, making python apps installable has always been a head-scratcher for me and it hasn't been easy to find content which address almost all aspects of the process with clear guidelines. You just made my life MUCH easier and I thank you for that.
Thank you for this great resource into the current mess of python packaging. It's something I've spent many hours trying to figure out, and now I know I missed a bunch. And with you handing a test setup on a silver platter, I now have no excuse to bring with formal testing. Once again, thank you. I really liked the longer format (when required) and am happy you didn't chop it up into parts. I would be really interested in similar in-depth videos on the things you mention in the video overview for example. If you could make a video on how to create a Python wrapper for a C library, I would be ecstatic.
Please make more videos like this. I've been having a lot of trouble when it comes to creating a github project. It's hard to find resources on project structure, git workflow, package structure, versioning, etc. If possible, it would be nice if you could create a series showing how to create and maintain a github repo. I want to understand how to increase versions, how to review pull requests and issues, how to write a good commit message, how to create tags/releases, how to create a documentation, and much more.
Don't feel like you have to watch it all at once. I see this very much as reference material that you can go back to over and over to get the bits you need. Thanks for watching!
@@mCoding I think this is great, that is just how i have / is currently using it. I have a small library mostly for internal use and can only fit in some time here and there for doing work on it. So this tutorial has taken a few weeks to test out and implement. But now i will feel much better doing changes to the library as i can much easier catch if (when) i break something. Cheers!
Project name: "Slap that like button" *with a characteristic look at the viewer LOL. You have really good oration. And good video, having recently implemented a lot of CI/CD stuff including this within the company I work for, it is great to see great tutorials on how to do this for others. Also, the great thing about fixtures is you can also return functions and classes and pass the parameters into that function inside the fixture by calling the fixture like fixture_name(args for the inner function of the fixture) or with a class you can also do fixture_name(args).method
This is one of the best and most complete python test setup guide I have ever seen in text or video form. While I knew about all the things mentioned here, your clear and incremental explanation has definitely helped me refresh everything and their interconnections. I am going to point every newbie (to testing) to this video hereafter. Thank you.
I recently moved to a new company that uses Python for it's automated tests suites. I've had to spin up very quickly and your videos have been very helpful. Thank you for making these!
The discussion on the project structure was fantastic, really insightful. It such an important aspect of a Python project, yet you don't see much information on it.
This video needs to be at millions of views this is the subtle additions to projects that add more depth to any code base and more to talk about during interviews and help you in sdnet QA and even site infrastructure developer
Outstanding video. The only people that say package management is the worst part of python are those that haven’t tried to decipher the topics you cover in this video. Might be time to revisit as the landscape is changing quickly. Also, more of this is welcome!
Thank you very much, the video is clear, it goes through multiples subject deep enough to be useful, but not deep enough to get a too long video. Also, the rythm is very cool, you don't get bored, you go point by point, and it's a good pace. Again, thanks !
the setup cfg work that allows you to traverse across different directories to get & apply code had been so difficult for me to find concise information on (I didn't want to do any os.dir nonsense, just wanted to make my project into a recognizable package) you explained it so well & so quickly, that's more than I could've asked for
I love this subject and I love this video. I'm glad this guy happened to make it a week ago, because it happens to be just what I need, when I need it. I'm stubbornly committing to TDD best-practices in my projects as I currently polish a template for my pytests.
I was originally only looking for TH-cam videos on pytest. With this video I found much more and it answered many questions that I have had regarding tox and GitHub integrations. Great video ... 👍👍👍
Thank you for this video, goes exactly at the right pace and gives the right amount of info. I've been struggling to setup this "testing" while coding setup (coding is not my specialty, but in mechanical engineering it's becoming unavoidable nowadays to automate more and more parts of our job). You've given me a much clearer picture of what to do and how to do it. Will definitely share this to my colleagues, great job!
I was looking on Udemy for some python testing courses. Then I found your video on youtube - I do not need Udemy anymore :D Thanks for the great video.
thanks a lot for this video. 4:14 & 7:37 > _"For automated testing, tests should run"_ [regardless the location of our source. Which's achieved by installing the project itself as a package.] i didn't understand the "import" part of the test_*.py files before, and got stuck there when i tried on my own several months ago. but this above part clears soo many things and i finally got my python pytests to work. thanks a lottttt again. i came here from binge watching ur latest video on python debugging. it just so happened that i was just restarting my python devt journey this time & was actually searching for some resource on pytest myself as the official doc didn't help at all. so, thanks for tooting this video there too.
not to self: * for applications using CLI arguments, do NOT use sys.argv directly. * use it via the formal parameter to the function (and set that to None by default). * this is similar to how c/java have `String[] args` as their formal parameter. oh lol, yet another approach combined from c. * this would allow that function to be called programmatically. * ... which makes writing tests for it easier and running 'em _much much_ faster.
Thanks, I imagined a few ways of cutting it up but they just didn't make as much sense to me. I'm glad I went with this version (even though it's probably not going to get as many views, I think it's worth it).
This is what I was looking for. Many thanks for covering these topics. I was specifically looking for how to install local package in current env, finally someone explained.
An excellent companion video would be a docker file that includes the repo in this package and talks to a docker postgresql instance. I currently use a Makefile to document commands and make development easier. Such as mounting a local directory for daily development.
This is very cool and interesting. As a physics student I mainly just plug and play but good to know about all of this, especially that it seems just as 'fiddly' as using a makefile or cmake with C/C++ and external libraries.
I am very grateful for this video because this is when all the setuptools pyproject.toml setup.py setup.cfg etc. finally made sense to me, aside from the actual automated testing :-)
thanks to this, im finally feeling confident enough to release this one project I've been working on for reading binary data for fun. I've also just now realized how tedious getting testing to work can be, 14 commits later it works on all devices (3.8+ though because i guess Literal types are pretty new)
Thank you a lot @mCoding, it was a well-structured tutorial. It would be very fantastic if you make an additional tutorial that covers automated testing on Gitlab.
Am I missing something, or when you write the tox.ini are you forgetting to install the standard dependencies? Seems like it wouldn't make sense to repeat the standard dependencies in the development dependencies
i had to cobble this knowledge together from documentation of all the features piece by piece over the course of a day and you just did it in half an hour (less, since i actually already had unittests) :D
Excellent walkthrough! 😊 Thanks for describing the current state of affairs and where things are headed. I hope we don't end up in a situation where this gets so complex that it drives new comers away from Python. I am already on the fence when it comes to the type hint craziness.
I've thought about this but in practice i rarely ever use cookiecutter, even though i follow templates. I just like to put the project together manually as it helps me remember what all the pieces are.
An excellent walk-through. I have shied away from even trying to set up something like this. Now I a) know I was right, and b) have a path to follow. Even just the part about "installable package": I have occasionally had to struggle with the situation that IDE, latest and other tools had different opinions on what the root directory was. So, for example, latest would run fine on the command line but fail to find the modules when run via the IDE. I hope that much of that will go away when I add the setuptools boilerplate.
7:25 “It’s a good practice to get very specific version numbers” Because most of PyPi packages use semantic versioning (or some major.minor scheme) , I think it’s better to use the ~= operator to get the latest minor/major release of the dependency. That way you get improvements or bug/security fixes without manual intervention. If tests fail because of a dependency, then you can either fix your own code or revert to a specific version that does work.
It's more than just common practice, semantic versioning is law: www.python.org/dev/peps/pep-0440/. The requirements.txt is more about deployment reproducibility, so it is more appropriate to use exact versions in your requirements file so that you get the exact same result on every deployment. The use of ~= wouldn't hurt in most cases, but when I push to prod I want the exact versions of everything specified, no guessing allowed. To me, ~= seems more appropriate for abstract dependencies (in the setup.py/setup.cfg), but I suppose my opinion on this matter isn't authoritative.
@@mCoding that’s a good point. It is a possibility that a patch would break your deployment. I think a good compromise would be to have some sort of a lock file like many other languages do 😅
why both setup.cfg and requirements files contains list of packages we need ? it's redundant, so mayby we could simplify and add reference to req file in setup.cfg ?
I'm getting there in a future video for sure! I'm sure you know there are just so many things you can do in CI/CD and it was just too much to fit it all in! But I'll get there eventually.
@@mCoding Of course... thank you! Do I need to have all of these versions of python 3.6-3.9 installed on my machine to have tox working? I'm getting interpreter not found errors for 3.6-8, but 3.9 (which I have installed) is working.
Finally someone discussing project setup, directory structure, git workflows etc. There needs to be more videos like this.
Very welcome! Thanks for watching.
superb!
@@mCoding incredible work son.
totally agree!
Please, more videos on this!
True! need more videos on this topic
I've been blindly pattern matching for spinning up repos for awhile now and it's nice to see explanations for a lot of those choices. I also didn't realize all the pytest functionality I was missing. I like this longer/more detailed style too - it's necessary for training strong engineers. (Though, not sure if it's the best choice for TH-cam growth). Thanks for making this. I'll be recommending it to coworkers.
We'll see how this one performs. I already have a pretty sophisticated audience so maybe they'll love it! If not I'm fine with a video tanking now and again, I know some people will still find it useful. Thanks for watching as always!
@@mCoding man you are the only one with real content, with the aim to teach beyond basics. your structure is awesome. the editing style is top notch. keep it up please. you are great
Utterly brilliant walkthrough!
Our company is currently implementing automated testing for a new project and all config requirements have worried me that I have no clue what's going on and would have no clue if stuff went wrong!
This is so clearly explained and motivated, I feel perfectly equipped to ensure we can implement it all and know all our tests are run!
Amazing! I'm so glad I was able to help. Thanks for sharing 👍
TH-cam is my Netflix when it comes to content related to programming, databases and DevOps, so I go through a ton of content regularly. but this video was one of THE most informative pieces of content I've ever watched. As a lower-intermediate Python programmer, making python apps installable has always been a head-scratcher for me and it hasn't been easy to find content which address almost all aspects of the process with clear guidelines. You just made my life MUCH easier and I thank you for that.
Glad I could help! Thanks for sharing.
Thank you for this great resource into the current mess of python packaging. It's something I've spent many hours trying to figure out, and now I know I missed a bunch. And with you handing a test setup on a silver platter, I now have no excuse to bring with formal testing.
Once again, thank you. I really liked the longer format (when required) and am happy you didn't chop it up into parts.
I would be really interested in similar in-depth videos on the things you mention in the video overview for example. If you could make a video on how to create a Python wrapper for a C library, I would be ecstatic.
You're welcome! Noted on those suggestions. I have a huge list of stuff to get to ... eventually 😀
Please make more videos like this. I've been having a lot of trouble when it comes to creating a github project. It's hard to find resources on project structure, git workflow, package structure, versioning, etc. If possible, it would be nice if you could create a series showing how to create and maintain a github repo. I want to understand how to increase versions, how to review pull requests and issues, how to write a good commit message, how to create tags/releases, how to create a documentation, and much more.
Was literally trying to figure out testing for the past week, its like you know exactly what I'm struggling on!
Great video as always
Great to hear I was able to help (again?)! 😀
one of the most important python tutorials I have ever seen. It covers a wide range of daily problems as python programmer.
Wow thank you! Glad you enjoyed 😀
The perfect amount of info to get started with automated testing. Thank you!
Glad you enjoyed it! Thanks so much for the kind words!
This is by far your most advanced tutorial. Too much info in a single video but still super helpful. Thanks !
Don't feel like you have to watch it all at once. I see this very much as reference material that you can go back to over and over to get the bits you need. Thanks for watching!
@@mCoding I think this is great, that is just how i have / is currently using it. I have a small library mostly for internal use and can only fit in some time here and there for doing work on it. So this tutorial has taken a few weeks to test out and implement. But now i will feel much better doing changes to the library as i can much easier catch if (when) i break something. Cheers!
Project name: "Slap that like button" *with a characteristic look at the viewer LOL.
You have really good oration. And good video, having recently implemented a lot of CI/CD stuff including this within the company I work for, it is great to see great tutorials on how to do this for others.
Also, the great thing about fixtures is you can also return functions and classes and pass the parameters into that function inside the fixture by calling the fixture like fixture_name(args for the inner function of the fixture) or with a class you can also do fixture_name(args).method
Thanks for your kind words. Glad you found my video useful!
This is one of the best and most complete python test setup guide I have ever seen in text or video form. While I knew about all the things mentioned here, your clear and incremental explanation has definitely helped me refresh everything and their interconnections. I am going to point every newbie (to testing) to this video hereafter. Thank you.
Thank you very much i appreciate the recommendation!
I recently moved to a new company that uses Python for it's automated tests suites. I've had to spin up very quickly and your videos have been very helpful. Thank you for making these!
Great to hear! Best of luck at your new company!
Example code should be exemplary. I think you've done a good job.
The discussion on the project structure was fantastic, really insightful. It such an important aspect of a Python project, yet you don't see much information on it.
This is great, I agree, finally someone talking about how to package a python project
This video needs to be at millions of views this is the subtle additions to projects that add more depth to any code base and more to talk about during interviews and help you in sdnet QA and even site infrastructure developer
We're on our way! Tell your friends and coworkers 😀
Outstanding video. The only people that say package management is the worst part of python are those that haven’t tried to decipher the topics you cover in this video. Might be time to revisit as the landscape is changing quickly. Also, more of this is welcome!
Thank you very much, the video is clear, it goes through multiples subject deep enough to be useful, but not deep enough to get a too long video.
Also, the rythm is very cool, you don't get bored, you go point by point, and it's a good pace.
Again, thanks !
You're welcome! Glad you enjoyed it.
Thanks a lot, this helped me in many ways. I'm currently working as a software developer but new to this field. And I did slap that like button.
Thanks very much!
the setup cfg work that allows you to traverse across different directories to get & apply code had been so difficult for me to find concise information on (I didn't want to do any os.dir nonsense, just wanted to make my project into a recognizable package)
you explained it so well & so quickly, that's more than I could've asked for
Very glad I could provide some help!
I love this subject and I love this video.
I'm glad this guy happened to make it a week ago, because it happens to be just what I need, when I need it. I'm stubbornly committing to TDD best-practices in my projects as I currently polish a template for my pytests.
I was originally only looking for TH-cam videos on pytest. With this video I found much more and it answered many questions that I have had regarding tox and GitHub integrations.
Great video ... 👍👍👍
Thank you for this video, goes exactly at the right pace and gives the right amount of info. I've been struggling to setup this "testing" while coding setup (coding is not my specialty, but in mechanical engineering it's becoming unavoidable nowadays to automate more and more parts of our job). You've given me a much clearer picture of what to do and how to do it. Will definitely share this to my colleagues, great job!
Happy to help! Thanks for watching!
I was looking on Udemy for some python testing courses. Then I found your video on youtube - I do not need Udemy anymore :D Thanks for the great video.
Really solid and easy to follow walkthrough, I really enjoy your clear and concise style.
Thanks so much for the kind words!
This video has a lot of useful content which is very rare these days
Many thanks!
thanks a lot for this video.
4:14 & 7:37 > _"For automated testing, tests should run"_ [regardless the location of our source. Which's achieved by installing the project itself as a package.]
i didn't understand the "import" part of the test_*.py files before, and got stuck there when i tried on my own several months ago.
but this above part clears soo many things and i finally got my python pytests to work. thanks a lottttt again.
i came here from binge watching ur latest video on python debugging. it just so happened that i was just restarting my python devt journey this time & was actually searching for some resource on pytest myself as the official doc didn't help at all. so, thanks for tooting this video there too.
not to self:
* for applications using CLI arguments, do NOT use sys.argv directly.
* use it via the formal parameter to the function (and set that to None by default).
* this is similar to how c/java have `String[] args` as their formal parameter. oh lol, yet another approach combined from c.
* this would allow that function to be called programmatically.
* ... which makes writing tests for it easier and running 'em _much much_ faster.
I saw your poll about this being long. Long was the right choice
Thanks, I imagined a few ways of cutting it up but they just didn't make as much sense to me. I'm glad I went with this version (even though it's probably not going to get as many views, I think it's worth it).
Holy shoot! Sooo many Nuggets in here! Thanks a lot! Very much appreciated!
You're very welcome!
Thank you, very useful!
You're welcome!
I have been a month looking for this video. Thanks for explaining how to properly create and install a package.
You are very welcome! I'm glad it was useful to you.
This is what I was looking for. Many thanks for covering these topics. I was specifically looking for how to install local package in current env, finally someone explained.
An excellent companion video would be a docker file that includes the repo in this package and talks to a docker postgresql instance. I currently use a Makefile to document commands and make development easier. Such as mounting a local directory for daily development.
Absolutely bookmarking this for the future. You just saved future me probably weeks of work
I still go back and watch it myself from time to time! Always good to write things down!
This is very cool and interesting. As a physics student I mainly just plug and play but good to know about all of this, especially that it seems just as 'fiddly' as using a makefile or cmake with C/C++ and external libraries.
Your hair looks like a softmax activation function
Hahahaah first time I've heard that one!
hahahahaha nice one
I am very grateful for this video because this is when all the setuptools pyproject.toml setup.py setup.cfg etc. finally made sense to me, aside from the actual automated testing :-)
Thanks for this very nice tutorial!
I wanna also learn all the things that you mentioned that you're not gonna discuss them in this video.
Great video! This is one of those topics many people have wondered about but haven't explored themselves.
Glad you enjoyed it!
This is a great guideline for getting started! Thanks a lot!
You're welcome thanks for watching!
Excellent video man, so clear and thorough.
Thank you very much, glad you enjoyed!
thanks to this, im finally feeling confident enough to release this one project I've been working on for reading binary data for fun. I've also just now realized how tedious getting testing to work can be, 14 commits later it works on all devices (3.8+ though because i guess Literal types are pretty new)
Awesome thanks for sharing!
Great video. A good amount of substance in under 30m... Deep enough without going too deep.
You're a star as always, eagerly waiting for you new videos
Truly great and quality content.
There should be more videos about this kind of topics.
Please, more on this! Thanks
That was a lot of pure content. Just perfect! Subscribed: D
Good luck, I believe in you ;)
Thank you a lot @mCoding, it was a well-structured tutorial. It would be very fantastic if you make an additional tutorial that covers automated testing on Gitlab.
The video was super useful so I SLAPPED LIKE NOW!
Thanks!
Great content, I liked it! I have been looking for TH-cam videos with pytest for unit tests in ML as part of the project setup. Thanks!
Great video, but a little bit tough for beginner.
I'll watch again:)
This is definitely a more intermediate level video and props for giving it an honest try even if you are a beginner! Good habits can go a long way!
I'm probably gonna watch this a few times.
Thanks! Glad it is helpful!
Thanks. I used `unittest` but this guide worked well enough.
Am I missing something, or when you write the tox.ini are you forgetting to install the standard dependencies?
Seems like it wouldn't make sense to repeat the standard dependencies in the development dependencies
i had to cobble this knowledge together from documentation of all the features piece by piece over the course of a day
and you just did it in half an hour (less, since i actually already had unittests) :D
Excellent walkthrough! 😊 Thanks for describing the current state of affairs and where things are headed. I hope we don't end up in a situation where this gets so complex that it drives new comers away from Python. I am already on the fence when it comes to the type hint craziness.
Very impressive! SLAPP LIKE NOW
This video is a gem 💎 congratulations
This is very useful information. Thank you. It would be great to also see automated documentation via sphinx or another alternative.
Amazing walkthrough!
Thanks! It might be about time to update it... !
"...you guessed it, another configuration file!" :))
This is exactly what I needed. Thanks so much !
Great to hear you found it useful! 😀
Very informative tutorial and glad to know I've been implementing these processes in my current projects with effectiveness 😅
Good job mCoding.. more like this on pytest, hypothesis, asyncio, flask etc.. punchy, high signal to noise ratio. Well done. Have subscribed.
16:07 > _"making a fixture called capture_stdout"_
now, there's pytest's inbuilt fixture: "capsys" to capture sys.stdout etc stuff. :)
Awesome! So understandable and straightforward
Glad to hear you liked it! Thanks for watching!
this was so clear and comprehensive...
Thanks!
Very high quality video
This is insanely good OMG
Amazing tutorial - comprehensive coverage and clear explanations. Thank you sir.
Very welcome!
What do you think about the python-cookiecutter and the tools used in the hypermodern guide to python? Could be a cool video too.
I've thought about this but in practice i rarely ever use cookiecutter, even though i follow templates. I just like to put the project together manually as it helps me remember what all the pieces are.
Thank you so much! Now I *AM* COOOLLLLLL!!!!
😎👍
Great video, this will be my resource for setting up any project automation
Perfect amount of information.
Amazing work, keep it up.
Awesome, thank you!
Great tutorial! So much information.
Thats amazing man... thanks for the tutorial!
An excellent walk-through. I have shied away from even trying to set up something like this. Now I a) know I was right, and b) have a path to follow.
Even just the part about "installable package": I have occasionally had to struggle with the situation that IDE, latest and other tools had different opinions on what the root directory was. So, for example, latest would run fine on the command line but fail to find the modules when run via the IDE. I hope that much of that will go away when I add the setuptools boilerplate.
Thanks for a video! All of your videos are awesome! Keep making it.
You're very welcome and thank you for your kind words!
Extremely helpful video thank you, your channel is a goldmine for me.
Awesome material!
Good God...
So many config files
Remember when Python was supposed to be simple and high level? Lol, what a mess
Enjoy ;)
Awesome video, we need more videos about good software development practices
This guide helped a lot and was very well done. Thanks!
Very informative. Thanks for sharing!
Your're very welcome!
You're awesome! Thanks for sharing this information!
You're very welcome!
7:25
“It’s a good practice to get very specific version numbers”
Because most of PyPi packages use semantic versioning (or some major.minor scheme) , I think it’s better to use the ~= operator to get the latest minor/major release of the dependency.
That way you get improvements or bug/security fixes without manual intervention.
If tests fail because of a dependency, then you can either fix your own code or revert to a specific version that does work.
It's more than just common practice, semantic versioning is law: www.python.org/dev/peps/pep-0440/.
The requirements.txt is more about deployment reproducibility, so it is more appropriate to use exact versions in your requirements file so that you get the exact same result on every deployment. The use of ~= wouldn't hurt in most cases, but when I push to prod I want the exact versions of everything specified, no guessing allowed. To me, ~= seems more appropriate for abstract dependencies (in the setup.py/setup.cfg), but I suppose my opinion on this matter isn't authoritative.
@@mCoding that’s a good point. It is a possibility that a patch would break your deployment.
I think a good compromise would be to have some sort of a lock file like many other languages do 😅
print("Man, thanks for this video!")
subscription += 1
Slapped that like and subscribe buttons.. 😎👍
Very good video .. but I knew nothing about how these packages work .. definitely got something to learn
Glad it was helpful!
Awesome video, thanks a lot !
Thank you very much! It is very informative video. It helps
Great explanation of python CI/CD know-how, with nice multi-environments scalability, good job. Please consider the same video content for C/C++
why both setup.cfg and requirements files contains list of packages we need ? it's redundant, so mayby we could simplify and add reference to req file in setup.cfg ?
I just thought I was bad at projects, seeing all those config files and figuring there must be a better way that a better programmer would know.
Python will get there some day! For now, I hope this helps :)
One thing i would change is to use pre-commit hooks for the linting
I'm getting there in a future video for sure! I'm sure you know there are just so many things you can do in CI/CD and it was just too much to fit it all in! But I'll get there eventually.
this video is extremely useful👍
Tip for newcomers: use ruff instead of flake8 for linting... way faster
Really great content and video. Thank you. I will update my project with this new knowledge.
Glad it was helpful!
this is exactly what I needed 👍🏽
I'm glad you believe in me so much! Thanks!
@@mCoding Of course... thank you! Do I need to have all of these versions of python 3.6-3.9 installed on my machine to have tox working? I'm getting interpreter not found errors for 3.6-8, but 3.9 (which I have installed) is working.
Videos on topics u said "I wont be covering here".
Haha okay noted ✅
Awesome..😎
PS: I did slash that like 👍🏼 button 😅