IMPORT F3 INTELSOFT CODE
Doing from imports is ok when you only need a few names from the module, but it makes the code harder to read because you can't tell just by looking at a name where it comes from. The whole of the Module_5.Module_A module is imported, the difference is that the first form adds the name Module_5.Module_A to your namespace, and the second form adds the name method_x to your namespace. Or from Module_5.Module_A import method_x In that situation it's ok to put such additional imports at the top of that section rather than at the top of the file. And that code may need a module (eg argparse) that's not needed by the rest of the code. Section at the end for code that only gets run when the file is run as a script. Such files will normally have a if _name_ = '_main_': One minor exception to this rule is if you have code that only gets run when the file is designed to be both imported as a module and run directly as a command-line script. (In fact, it can be slightly less efficient if several of your classes import from the same module, since you're needlessly giving the interpreter more work to do, but it's not a big deal because the interpreter always checks to see if a module is already loaded before it attempts to read it from disk).
You can put imports inside class or function definitions, but there's no point, it makes the code harder to read, and there is no real benefit in doing so. Is there some performance implication for the classes that don't use the method_x if I import a method at the Module level, instead of at the class level? What is the 'usual' or the 'more pythonic' way (if there is such a think in this case), importing the method at the module level or at the class level when a) only one class in the module needs the imported method and when b) 1 < < need the imported method?Īs Gribouillis has mentioned it is customary to put all your import statements at the start of the file.
method_x) from another Module (again, in the _init_ method of each class). Imagine that two of my classes need the same method (e.g. I have a Module with, say, 10 classes and 30 methods.When I write Class_2, I have to import again in the _init_ method the methods imported in Class_1 or the inheritance implies also the methods imported at the Class_1 level?įrom Module_5.Module_A import method_x again? At the same time, I have some methods from yet another Module imported at the Class_1._init_ method level. And I have some doubts regarding the importation of methods/classes through various modules: Right now I've covered the essentials and I'm experimenting with my first app in python, so it's the first time that I practice with modules, inheritance and etc.
The thing is that I'm a total newbie, and I am learning programming through python and javascript. Also, I'm not an English native speaker, so be prepared for some grammar mistakes as well. This is my first question here in stackoverflow, so if I make one or two mistakes, please, let me now.
0 kommentar(er)
