How to import from the same package
up vote
0
down vote
favorite
I'm using Python 3 and Jupyter under Windows 10.
I have 2 modules: mod_main and mod_sub. I'd like to import various modules (in this case, only os) from mod_sub to mod_main. The approach that works for me is as follows:
mod_main.py
from pathlib import Path # works with / for any OS
import sys
sys.path.append(str(Path('C:/MyApps/Python_Base')))
from dummypackage.mod_sub import *
#from dummypackage import mod_sub
def print_path():
print(os.path.realpath(__file__))
mod_sub.py
import os
print('mod_sub is imported')
I then run the following from a Jupyter Notebook under C:MyAppsPython_Base
from dummypackage import mod_main
import importlib
importlib.reload(mod_main)
mod_main.print_path()
Now, I have a couple of questions:
- use of wildcards is discouraged, but if I use
from dummypackage import mod_subthen I won't get access to other imported modeules (osin this case). So, what is the best practice here? - is there any better ways to import a module from the same package? what I did to add the path to the parent folder and the import from package.module looks ugly. Is there a better way to do so?
python path jupyter-notebook python-import python-module
edited Nov 11 at 16:52
Flimzy
36.8k96496
asked Nov 11 at 16:47
towi_parallelism
664818
|
show 4 more comments
up vote
0
down vote
favorite
I'm using Python 3 and Jupyter under Windows 10.
I have 2 modules: mod_main and mod_sub. I'd like to import various modules (in this case, only os) from mod_sub to mod_main. The approach that works for me is as follows:
mod_main.py
from pathlib import Path # works with / for any OS
import sys
sys.path.append(str(Path('C:/MyApps/Python_Base')))
from dummypackage.mod_sub import *
#from dummypackage import mod_sub
def print_path():
print(os.path.realpath(__file__))
mod_sub.py
import os
print('mod_sub is imported')
I then run the following from a Jupyter Notebook under C:MyAppsPython_Base
from dummypackage import mod_main
import importlib
importlib.reload(mod_main)
mod_main.print_path()
Now, I have a couple of questions:
- use of wildcards is discouraged, but if I use
from dummypackage import mod_subthen I won't get access to other imported modeules (osin this case). So, what is the best practice here? - is there any better ways to import a module from the same package? what I did to add the path to the parent folder and the import from package.module looks ugly. Is there a better way to do so?
python path jupyter-notebook python-import python-module
edited Nov 11 at 16:52
Flimzy
36.8k96496
asked Nov 11 at 16:47
towi_parallelism
664818
What about from . import ModuleName ?
– quant
Nov 11 at 17:04
that again takes me to the first problemNameError: name 'os' is not defined. I though from package import module imports everything, but I was wrong
– towi_parallelism
Nov 11 at 17:11
Why not justimport dummypackage? Then you have access to everything.
– Ayxan
Nov 11 at 17:15
No, I won't.oswill still remain undefined
– towi_parallelism
Nov 11 at 17:19
1
@towi_parallelism I'm saying that your claim that you won't get access to other import modules is incorrect - you should probably change your style and not import a wildcard and not rely on the submodule importing libraries that you want access to
– n8sty
Nov 12 at 17:09
|
show 4 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm using Python 3 and Jupyter under Windows 10.
I have 2 modules: mod_main and mod_sub. I'd like to import various modules (in this case, only os) from mod_sub to mod_main. The approach that works for me is as follows:
mod_main.py
from pathlib import Path # works with / for any OS
import sys
sys.path.append(str(Path('C:/MyApps/Python_Base')))
from dummypackage.mod_sub import *
#from dummypackage import mod_sub
def print_path():
print(os.path.realpath(__file__))
mod_sub.py
import os
print('mod_sub is imported')
I then run the following from a Jupyter Notebook under C:MyAppsPython_Base
from dummypackage import mod_main
import importlib
importlib.reload(mod_main)
mod_main.print_path()
Now, I have a couple of questions:
- use of wildcards is discouraged, but if I use
from dummypackage import mod_subthen I won't get access to other imported modeules (osin this case). So, what is the best practice here? - is there any better ways to import a module from the same package? what I did to add the path to the parent folder and the import from package.module looks ugly. Is there a better way to do so?
python path jupyter-notebook python-import python-module
edited Nov 11 at 16:52
Flimzy
36.8k96496
asked Nov 11 at 16:47
towi_parallelism
664818
I'm using Python 3 and Jupyter under Windows 10.
I have 2 modules: mod_main and mod_sub. I'd like to import various modules (in this case, only os) from mod_sub to mod_main. The approach that works for me is as follows:
mod_main.py
from pathlib import Path # works with / for any OS
import sys
sys.path.append(str(Path('C:/MyApps/Python_Base')))
from dummypackage.mod_sub import *
#from dummypackage import mod_sub
def print_path():
print(os.path.realpath(__file__))
mod_sub.py
import os
print('mod_sub is imported')
I then run the following from a Jupyter Notebook under C:MyAppsPython_Base
from dummypackage import mod_main
import importlib
importlib.reload(mod_main)
mod_main.print_path()
Now, I have a couple of questions:
- use of wildcards is discouraged, but if I use
from dummypackage import mod_subthen I won't get access to other imported modeules (osin this case). So, what is the best practice here? - is there any better ways to import a module from the same package? what I did to add the path to the parent folder and the import from package.module looks ugly. Is there a better way to do so?
python path jupyter-notebook python-import python-module
python path jupyter-notebook python-import python-module
edited Nov 11 at 16:52
Flimzy
36.8k96496
asked Nov 11 at 16:47
towi_parallelism
664818
edited Nov 11 at 16:52
Flimzy
36.8k96496
asked Nov 11 at 16:47
towi_parallelism
664818
edited Nov 11 at 16:52
Flimzy
36.8k96496
edited Nov 11 at 16:52
Flimzy
36.8k96496
edited Nov 11 at 16:52
Flimzy
36.8k96496
36.8k96496
asked Nov 11 at 16:47
towi_parallelism
664818
asked Nov 11 at 16:47
towi_parallelism
664818
asked Nov 11 at 16:47
towi_parallelism
664818
664818
What about from . import ModuleName ?
– quant
Nov 11 at 17:04
that again takes me to the first problemNameError: name 'os' is not defined. I though from package import module imports everything, but I was wrong
– towi_parallelism
Nov 11 at 17:11
Why not justimport dummypackage? Then you have access to everything.
– Ayxan
Nov 11 at 17:15
No, I won't.oswill still remain undefined
– towi_parallelism
Nov 11 at 17:19
1
@towi_parallelism I'm saying that your claim that you won't get access to other import modules is incorrect - you should probably change your style and not import a wildcard and not rely on the submodule importing libraries that you want access to
– n8sty
Nov 12 at 17:09
|
show 4 more comments
What about from . import ModuleName ?
– quant
Nov 11 at 17:04
that again takes me to the first problemNameError: name 'os' is not defined. I though from package import module imports everything, but I was wrong
– towi_parallelism
Nov 11 at 17:11
Why not justimport dummypackage? Then you have access to everything.
– Ayxan
Nov 11 at 17:15
No, I won't.oswill still remain undefined
– towi_parallelism
Nov 11 at 17:19
1
@towi_parallelism I'm saying that your claim that you won't get access to other import modules is incorrect - you should probably change your style and not import a wildcard and not rely on the submodule importing libraries that you want access to
– n8sty
Nov 12 at 17:09
What about from . import ModuleName ?
– quant
Nov 11 at 17:04
What about from . import ModuleName ?
– quant
Nov 11 at 17:04
that again takes me to the first problem
NameError: name 'os' is not defined. I though from package import module imports everything, but I was wrong– towi_parallelism
Nov 11 at 17:11
that again takes me to the first problem
NameError: name 'os' is not defined. I though from package import module imports everything, but I was wrong– towi_parallelism
Nov 11 at 17:11
Why not just
import dummypackage ? Then you have access to everything.– Ayxan
Nov 11 at 17:15
Why not just
import dummypackage ? Then you have access to everything.– Ayxan
Nov 11 at 17:15
No, I won't.
os will still remain undefined– towi_parallelism
Nov 11 at 17:19
No, I won't.
os will still remain undefined– towi_parallelism
Nov 11 at 17:19
1
1
@towi_parallelism I'm saying that your claim that you won't get access to other import modules is incorrect - you should probably change your style and not import a wildcard and not rely on the submodule importing libraries that you want access to
– n8sty
Nov 12 at 17:09
@towi_parallelism I'm saying that your claim that you won't get access to other import modules is incorrect - you should probably change your style and not import a wildcard and not rely on the submodule importing libraries that you want access to
– n8sty
Nov 12 at 17:09
|
show 4 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53250949%2fhow-to-import-from-the-same-package%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What about from . import ModuleName ?
– quant
Nov 11 at 17:04
that again takes me to the first problem
NameError: name 'os' is not defined. I though from package import module imports everything, but I was wrong– towi_parallelism
Nov 11 at 17:11
Why not just
import dummypackage? Then you have access to everything.– Ayxan
Nov 11 at 17:15
No, I won't.
oswill still remain undefined– towi_parallelism
Nov 11 at 17:19
1
@towi_parallelism I'm saying that your claim that you won't get access to other import modules is incorrect - you should probably change your style and not import a wildcard and not rely on the submodule importing libraries that you want access to
– n8sty
Nov 12 at 17:09