Hello everyone! Another user was having a problem that I want to share with you guys. When you import a package to python, the interpreter searches several paths to find your library - one of which being the working directory. If, however, one of those other paths has a library with the same name, that one will take precedence! If you create a library called Matplotlib, python will still import the original instead of yours!
I came here to learn __init__, but the way you have demonstrated is absolutely amazing; now I understand what from, import, and __init__.py do. Brilliant!.
Slight correction. I haven’t finished watching it yet. But if you do import resources.object_ones. You can do object_ones.Ones(). That’s it. It’s more to type, which is why the from is used. But you will often see packages like pandas like this. import pandas as pd. Then we do pd.DataFrame() blah blah.
Jeeez I always used init files without typing in anything. 2 years passed here I am finding out this blessing of information. This will clean up a lot of mess in my projects. Huge thanks!!!!!
Thank you! The first two minutes explained my confusion about why some of my code would work without errors when other code wouldn't. Definitely helped me. Thanks!!!
Great! I was reading tutorials about python to grasp everything. Not a great idea. It was confusing especially the __init__ but your videos makes it so easy to understand! Love it. Thank you so much
randomly came across and whatever this is, this helped me understand soo much init and the concept of library, in such a short and engaging video. thank you so much.
Thank you for this. You're a good teacher and your explanations are clear. I was struggling because all the answers were "just append the directory to the system path" or "put it in the init file" with no information on WHAT to put in the file.
Very good explanation. I was wondering why a lot of projects had hundreds of lines of code added to their __init__ file and this has helped a lot. Thanks mate!
Thank you so much for this video! However, I was wondering if we could simply use "from resources import *" to avoid specifying which object we're trying to import? Thanks for your help!
Really good explanation Eric! you are really the first TH-camr that explained it so good that i can understand it right away without becoming confused xD. You got my sub :)
5:25 is there another solution to copy and paste the resources? For example, i want to share common resources among many projects, and I dont want to have to maintain copies. Thank you!
Why do you have to write “from resources.object_one import One” in the init file when it’s already inside of the resources folder. I would’ve thought the line should be just “from object_one import One” 🤔. Is this something to do with where the cwd is?
What I missing here, resources.one() throwing me an error bcz i am bypassing object_one file. when I do import resources.object_one as one and then o = one.One() works fine
Just curious, what does a blank __init__.py file do in this case? Until this video, everywhere I looked was saying "oh just create an empty __init__.py file and it should work", guess what, it never worked. Thanks for the video, that was very helpful.
When i just joined a python project (it was Django based) i noticed those __init__ files almost in every directory. They also referred to each other in a quite chaotic way. Few years later i started working on my own projects (this time fastapi) and the things do not seem to be clear still. I noticed very weird things - e.g. my main file may work fine, but when i run my tests (which use the main file) i get errors "package 'xyz' is not found". It looks like there is a lot of magic in terms of visibility of packages. Sometimes they can see parent packages, sometimes cannot. Thee is also that feature of relative import which also behaves not as expected sometimes. So yeah i have difficult times understanding the idea nd how to structure my projects.
yeah but with filling init file with import statements, we just made imported modules depend on each other. so in this case object_one module now depends on object_two module, no? if I wanted to import object_one module, it will automatically try to load object_two module also. how do we avoid this completely? it is driving me crazy sometimes
I understood this concept now, One favor I want, How do we manage the different configurations(DevelopentConfig, QAConfig, ProductionConfig), They hold the variables that are used in all over the project, is there any way that we can mention if we want to use DevelopmentConfig or ProductionConfig without changing lots of code?
You would either create another _init__.py or move the files in such a way that you can call them. Think if the libraries as if they are in a file structure. As long as the Python_path has the folders in the parent path then you can call them. This is about not having to recall functions over and over again and being able to utilize one file to establish everything in a collective state.,
I need help. I am making an app and I need to import modules from a different folder and I can't get any solutions on internet. Can I just build one __init__.py file in the folder and will it work just like this as I don't want to involve the IDLE in this case is it possible only through script editor??
Typically, using full paths will be helpful here. ~/project/import is more likely to cause problems than /home/me/project/import. That being said, it may be wise to package all of these imports together into a single environment directory that will contain everything needed for the project.
Another use of __init__.py file is to provide an interface so if you change structure of package you only need to change the init file and not other imports in your client code.
I don't know what's the problem but mine is not working , I copied the same code but at the end compiler says from abc.one import One ModuleNotFoundError: No module named 'abc.one'; 'abc' is not a package
Do you mind telling me what your directory structure is? If you want to jump on to the discord it would be easier to help you debug. discord.gg/PTWecyAbDU
Is it possible to write conditional import statements in __init__.py ? i mean, If I have a package with 50 files and I want to use 10 among them in one case and in another case, I want to use 30 among them.
Nice video though I think there might be a possible issue with using an __init__ file and I may be wrong however I can't seem to find anything on this. Hypothetically speaking you could have all your [from foo import bar's] in an __init__ file but can't this make circular imports? You have four files, A B, C and D each with their import in the __init__ (from A import a etc) A needs B B needs C C needs the other 2 Doesn't this mean a Circular import will happen due to B getting C and C getting B due to the __init__ file as all imports from the __init__ file are "pushed" into each document that calls it
That was straight up to the point. Can you make more vids on tricky parts of python? Some concepts might be challenging to wrap your head around, especially from someone coming from other languages.
Thank you, I try to make videos like these as the topic comes up in my daily workflow. If you point something out to me, though, I'd be happy to make a video on it.
@@eom-dev I have some topics in mind. How to structure a python code since, I have noticed that untyped languages are not ideal for big projects. And another topic that would have been sweet is software development architecture styles. Those two topics always come up together.
I think you could call these two functions without assigning them to variables. You could write: resources.One() resources.Two() Instead of: o = resources.One() t = resources.Two() You will get the same result.
Hello everyone! Another user was having a problem that I want to share with you guys. When you import a package to python, the interpreter searches several paths to find your library - one of which being the working directory. If, however, one of those other paths has a library with the same name, that one will take precedence! If you create a library called Matplotlib, python will still import the original instead of yours!
Finally a short and to the point tutorial that actually tells me what the frick a __init__.py is and how to use it, thank you!
I came here to learn __init__, but the way you have demonstrated is absolutely amazing; now I understand what from, import, and __init__.py do. Brilliant!.
Thank you! I appreciate it!
Same! Good job
Slight correction. I haven’t finished watching it yet. But if you do import resources.object_ones. You can do object_ones.Ones(). That’s it. It’s more to type, which is why the from is used. But you will often see packages like pandas like this. import pandas as pd. Then we do pd.DataFrame() blah blah.
Jeeez I always used init files without typing in anything. 2 years passed here I am finding out this blessing of information. This will clean up a lot of mess in my projects. Huge thanks!!!!!
Thank you! The first two minutes explained my confusion about why some of my code would work without errors when other code wouldn't. Definitely helped me. Thanks!!!
That was what my problem
This was the 'dark souls boss' of python for me. You executed him in under 6 minutes. Thank you sensei.
concise, short, to the point, just what I was expecting
You're a gem! Such a great teacher! If everyone taught like this anyone could learn Python in days!
One of the best explanations I've heard on the subject. Thanks!
Short and straightforward, great work Eric!
Great! I was reading tutorials about python to grasp everything. Not a great idea. It was confusing especially the __init__ but your videos makes it so easy to understand! Love it. Thank you so much
randomly came across and whatever this is, this helped me understand soo much init and the concept of library, in such a short and engaging video. thank you so much.
OH MY GOD it's so simple yet noone has ever explained it like this!!!
this might be the best explanation about imports on youtube. thanks man
Thank you for this. You're a good teacher and your explanations are clear.
I was struggling because all the answers were "just append the directory to the system path" or "put it in the init file" with no information on WHAT to put in the file.
One of the better explanations i have seen on youtube!
Thank you!
Thanks for that clear description. This make reusing code so much easier. I have been trying to figure this out for two weeks.
It takes an altogether different mind to even bother about this aspect!! Thanks.
i dont see how this video could have been better. thank you
Short and straight to the point. I love this!
Thanks, no confusing words used. Clearly explained!
Thank you very much Eric, I sure appreciate you for this short informative video. Will support you till the end .
Much appreciated!
Thanks, Eric. This short video was just what I was looking for. I'm a Python newcomer and packages have been difficult to grok until now.
Very good explanation. I was wondering why a lot of projects had hundreds of lines of code added to their __init__ file and this has helped a lot. Thanks mate!
Super helpful! I love how you walked through the logic
Thank you so much for this video! However, I was wondering if we could simply use "from resources import *" to avoid specifying which object we're trying to import?
Thanks for your help!
Concise, clear and very informative. Thank you ❤
Oh my lord my eyes!!! You are one of like three people I’ve ever met that works in a light theme….
Really good explanation Eric! you are really the first TH-camr that explained it so good that i can understand it right away without becoming confused xD. You got my sub :)
Thank you! Feel free to join our discord server if you have any questions! I'm happy to help :)
subscriber number 382 here.
great content. to the point. thanks
Thanks for the sub, welcome aboard!
Broo, you are a genius. Thank you for explaining it so clearly. Subbed and liked!
Superb succinct tutorial - many thanks!
You are very good at explaining things. Great video!
Extremely helpful and very well explained.
I think you can also write something like __add__ = ["object_one", "object_two"] inside of this __init__.py file.
Thanks a lot mate, was trying for ages this.. but resolved now. Thank you .
5:25 is there another solution to copy and paste the resources? For example, i want to share common resources among many projects, and I dont want to have to maintain copies. Thank you!
Hey, I am really struggling with relative imports. It would be great if you make a vid about it
can you please put library and code to different folders and access library. May be at the same level.
Thanks , this video help me to get more clear and easily understanadable information
Hi! Can I loop through files and import them at run time? I don't know which files to import beforehand.
what if i have 2 directories and i want to import class from from dir1 into my file which is in dir2
Both dir in same path.
Thank you so much for this video. I find this topic relatively challenging to understand but now is completely clear for me. Thanks again.
Excellent! man, I will recommend your channel.
Why do you have to write “from resources.object_one import One” in the init file when it’s already inside of the resources folder. I would’ve thought the line should be just “from object_one import One” 🤔. Is this something to do with where the cwd is?
What I missing here, resources.one() throwing me an error bcz i am bypassing object_one file. when I do import resources.object_one as one and then o = one.One() works fine
Wow how come this guy have very less subscribers. you deserve more.
Just curious, what does a blank __init__.py file do in this case? Until this video, everywhere I looked was saying "oh just create an empty __init__.py file and it should work", guess what, it never worked. Thanks for the video, that was very helpful.
When i just joined a python project (it was Django based) i noticed those __init__ files almost in every directory. They also referred to each other in a quite chaotic way.
Few years later i started working on my own projects (this time fastapi) and the things do not seem to be clear still. I noticed very weird things - e.g. my main file may work fine, but when i run my tests (which use the main file) i get errors "package 'xyz' is not found". It looks like there is a lot of magic in terms of visibility of packages. Sometimes they can see parent packages, sometimes cannot. Thee is also that feature of relative import which also behaves not as expected sometimes.
So yeah i have difficult times understanding the idea nd how to structure my projects.
Thanks Mr.Eric. it's a good explanation... 🎉
So what is the purpose of having an empty __init__.py file? I've seen this in many projects...
If the __init__.py is empty in this case, the script fails. Why so ? Has class something to do with it ?
Just what I was looking for!
yeah but with filling init file with import statements, we just made imported modules depend on each other. so in this case object_one module now depends on object_two module, no? if I wanted to import object_one module, it will automatically try to load object_two module also. how do we avoid this completely? it is driving me crazy sometimes
for this to work, do I need to hit the keyboard as hard as you?
Very short and nice and clear explanation.
Clear and concise ... Good job!
It helps understand the concept better!
I understood this concept now, One favor I want,
How do we manage the different configurations(DevelopentConfig, QAConfig, ProductionConfig),
They hold the variables that are used in all over the project, is there any way that we can mention
if we want to use DevelopmentConfig or ProductionConfig without changing lots of code?
Congrats!! Very very well explained.
Thank you!
If tutorial.py present in another directory . How can we import resources
Waow, great explanation thank you so much. I was able to follow along :)
ok but what if tutorial.py has to import from a ../ dir?
Hi Eric, what if the modules you want to import are from a different directory (non-parental relationship)?
You would either create another _init__.py or move the files in such a way that you can call them. Think if the libraries as if they are in a file structure. As long as the Python_path has the folders in the parent path then you can call them. This is about not having to recall functions over and over again and being able to utilize one file to establish everything in a collective state.,
Straight to the point, thanks!
I need help. I am making an app and I need to import modules from a different folder and I can't get any solutions on internet. Can I just build one __init__.py file in the folder and will it work just like this as I don't want to involve the IDLE in this case is it possible only through script editor??
Typically, using full paths will be helpful here. ~/project/import is more likely to cause problems than /home/me/project/import. That being said, it may be wise to package all of these imports together into a single environment directory that will contain everything needed for the project.
Another use of __init__.py file is to provide an interface so if you change structure of package you only need to change the init file and not other imports in your client code.
Short and to the point. Great work Eric 👌
I think I would be coming back to you the next time as well for any help on python.
I don't know what's the problem
but mine is not working , I copied the same code but at the end compiler says
from abc.one import One
ModuleNotFoundError: No module named 'abc.one'; 'abc' is not a package
Do you mind telling me what your directory structure is? If you want to jump on to the discord it would be easier to help you debug.
discord.gg/PTWecyAbDU
Very nice and clear tutorial, it helps a lot!
Thanks! Understood it well and clear. The naming __init__.py is by convention, right?
Very useful and very clear. Thank you!
Is it possible to write conditional import statements in __init__.py ? i mean, If I have a package with 50 files and I want to use 10 among them in one case and in another case, I want to use 30 among them.
Thanks a lot Mr.Eric 😍😍
Thanks for the explanation, it's now clearer
Well done. Explained excellently.
Glad it was helpful!
Definitely useful 👍👍
Man it aint workin for me, for some reason it just say "No module named 'my_module' "
Awesome tutorial ........
Thanks You very much from France !
Nice video though I think there might be a possible issue with using an __init__ file and I may be wrong however I can't seem to find anything on this.
Hypothetically speaking you could have all your [from foo import bar's] in an __init__ file but can't this make circular imports?
You have four files, A B, C and D each with their import in the __init__ (from A import a etc)
A needs B
B needs C
C needs the other 2
Doesn't this mean a Circular import will happen due to B getting C and C getting B due to the __init__ file as all imports from the __init__ file are "pushed" into each document that calls it
Explained very well 👏
Great🎉 .Crystal clear ❤
Very beautifully explained brother
Thanks for the help! Really good explanation
Glad you liked it, thank you!
Excellent explanation, thank you
Simple but great work.. Thanks
The title of this video should be: "how to make a tutorial that lets you quickly learn something useful" 🙂
That was straight up to the point. Can you make more vids on tricky parts of python? Some concepts might be challenging to wrap your head around, especially from someone coming from other languages.
Thank you, I try to make videos like these as the topic comes up in my daily workflow. If you point something out to me, though, I'd be happy to make a video on it.
@@eom-dev I have some topics in mind. How to structure a python code since, I have noticed that untyped languages are not ideal for big projects. And another topic that would have been sweet is software development architecture styles. Those two topics always come up together.
Fantastic explanation!
I think you could call these two functions without assigning them to variables. You could write:
resources.One()
resources.Two()
Instead of:
o = resources.One()
t = resources.Two()
You will get the same result.
great explanation!
Thanks for this. I really needed to understand this.
Glad it was helpful!
This is really helpful. Thank you so much!
Thanks a ton Eric!!
Amazing! Thanks!
Brilliant explanation! Thank you:)
why didn't you use __all__
was awesome, cheers!
Glad you enjoyed it!
very helpful thanks!