I had the same problem, and solved it by adding a leading underscore to all my imports. It doesn’t look brilliant, but it achieves what you’re after. from __future__ import division as _division import numpy as _np import pandas as _pd Only the stuff that starts without an underscore is imported when you import the … Read more
Your package structure is OK. Your import statement is OK. The only thing missing is for the package to be visible in sys.path, a list of locations where import statements can be resolved. Usually we do this by “installing” the package locally with pip, which copies your code into site-packages†. This directory is one of … Read more
Yes, this file is required if you want directory to be treated as a module. The __init__.py files are required to make Python treat the directories as containing packages; this is done to prevent directories with a common name, such as string, from unintentionally hiding valid modules that occur later on the module search path. … Read more
Python adds the directory where the initial script resides as first item to sys.path: As initialized upon program startup, the first item of this list, path[0], is the directory containing the script that was used to invoke the Python interpreter. If the script directory is not available (e.g. if the interpreter is invoked interactively or … Read more
I strongly advise against what you want to do. You are doing the global include file mistake again. Although only one module is importing all your modules (as opposed to all modules importing the global one), the remaining point is that if there’s a valid reason for all those modules to be collected under a … Read more
I had faced the same problem. Restarting the notebook solved my problem. If that doesn’t solve the problem, you can try this pip install seaborn Edit As few people have posted in the comments, you can also use python -m pip install seaborn Plus, as per https://bugs.python.org/issue22295 it is a better way because in this … Read more
According to this really old mailing list post it works if you also have an __init__.py file (the __init__.py file is not used, but seems to be necessary for the directory to be treated as a module, and hence the __init__.so file to be loaded). If I add __init__.py: # an exception just to confirm … Read more
You will have to import something at least once per file. But you can set it up such that this is a single import line: The probably cleanest way is to create a folder lib, move all lib?.py in there, and add an empty file called __init__.py to it. This way you create a package … Read more
there are various approaches to do so, here is just a silly and simple one: main.py “””A silly example – main supplies a parameter “”” import sys,os print os.path.basename(__file__)+”:Push it by: –myModuleParam “+str(123) sys.argv.append(‘–myModuleParam’) sys.argv.append(123) import module print os.path.basename(__file__)+”:Pushed my param:”+str(module.displayMyParam) module.py “””A silly example – module consumes parameter “”” import sys,os displayMyParam = ‘NotYetInitialized’ … Read more
Yes, but it’ll only work as expected with fully qualified access paths to modules: import example example.examplemod.config.CONSTANT = “Better value” example.examplemod.do_stuff()