Avoiding duplication of namespace elements in python imports
This is probably a vestige from my days as a c# programmer, and I probably just need to learn the "pythonic" way of doing things. I'm relatively new to python, but have been coding in c# for years.
I have a python module within my project named 'applib' where I store a number of classes. Each class is contained within its own file of the same name (e.g. Foo.py has a class named Foo, Bar.py has a class named Bar, etc).
When I want to use a class, I have to say
import applib.Foo
followed by something like
my_foo=applib.Foo.Foo()
This results in having to specify "Foo" twice in my declaration (once for the module name, and then again for the class). In c# I could control this with a namespace directive at the top of the class file, but in python I don't know of a way to control this except for putting all my classes in a single file. I know I can also import the class by using
from applib.Foo import Foo
but that's still a duplication of namespace elements, which I want to avoid completely.
Can anyone provide me with some recommendations on a more pythonic methodology for namespace structure within an app?
python namespaces python-import
asked Nov 26 '18 at 23:47
NevDullNevDull
335
add a comment |
This is probably a vestige from my days as a c# programmer, and I probably just need to learn the "pythonic" way of doing things. I'm relatively new to python, but have been coding in c# for years.
I have a python module within my project named 'applib' where I store a number of classes. Each class is contained within its own file of the same name (e.g. Foo.py has a class named Foo, Bar.py has a class named Bar, etc).
When I want to use a class, I have to say
import applib.Foo
followed by something like
my_foo=applib.Foo.Foo()
This results in having to specify "Foo" twice in my declaration (once for the module name, and then again for the class). In c# I could control this with a namespace directive at the top of the class file, but in python I don't know of a way to control this except for putting all my classes in a single file. I know I can also import the class by using
from applib.Foo import Foo
but that's still a duplication of namespace elements, which I want to avoid completely.
Can anyone provide me with some recommendations on a more pythonic methodology for namespace structure within an app?
python namespaces python-import
asked Nov 26 '18 at 23:47
NevDullNevDull
335
2
don't write one module per class. Put all your classes inapplib.
– Daniel
Nov 26 '18 at 23:49
1
"Each class is contained within its own file of the same name" - bad idea. It causes all sorts of confusion, including mixing up classes and modules, and making things like circular import problems much more common.
– user2357112
Nov 26 '18 at 23:49
@Daniel. I'm confused. How would I set my directory structure up to reflect this?
– NevDull
Nov 27 '18 at 0:49
add a comment |
This is probably a vestige from my days as a c# programmer, and I probably just need to learn the "pythonic" way of doing things. I'm relatively new to python, but have been coding in c# for years.
I have a python module within my project named 'applib' where I store a number of classes. Each class is contained within its own file of the same name (e.g. Foo.py has a class named Foo, Bar.py has a class named Bar, etc).
When I want to use a class, I have to say
import applib.Foo
followed by something like
my_foo=applib.Foo.Foo()
This results in having to specify "Foo" twice in my declaration (once for the module name, and then again for the class). In c# I could control this with a namespace directive at the top of the class file, but in python I don't know of a way to control this except for putting all my classes in a single file. I know I can also import the class by using
from applib.Foo import Foo
but that's still a duplication of namespace elements, which I want to avoid completely.
Can anyone provide me with some recommendations on a more pythonic methodology for namespace structure within an app?
python namespaces python-import
asked Nov 26 '18 at 23:47
NevDullNevDull
335
This is probably a vestige from my days as a c# programmer, and I probably just need to learn the "pythonic" way of doing things. I'm relatively new to python, but have been coding in c# for years.
I have a python module within my project named 'applib' where I store a number of classes. Each class is contained within its own file of the same name (e.g. Foo.py has a class named Foo, Bar.py has a class named Bar, etc).
When I want to use a class, I have to say
import applib.Foo
followed by something like
my_foo=applib.Foo.Foo()
This results in having to specify "Foo" twice in my declaration (once for the module name, and then again for the class). In c# I could control this with a namespace directive at the top of the class file, but in python I don't know of a way to control this except for putting all my classes in a single file. I know I can also import the class by using
from applib.Foo import Foo
but that's still a duplication of namespace elements, which I want to avoid completely.
Can anyone provide me with some recommendations on a more pythonic methodology for namespace structure within an app?
python namespaces python-import
python namespaces python-import
asked Nov 26 '18 at 23:47
NevDullNevDull
335
asked Nov 26 '18 at 23:47
NevDullNevDull
335
asked Nov 26 '18 at 23:47
NevDullNevDull
335
asked Nov 26 '18 at 23:47
NevDullNevDull
335
asked Nov 26 '18 at 23:47
NevDullNevDull
335
335
2
don't write one module per class. Put all your classes inapplib.
– Daniel
Nov 26 '18 at 23:49
1
"Each class is contained within its own file of the same name" - bad idea. It causes all sorts of confusion, including mixing up classes and modules, and making things like circular import problems much more common.
– user2357112
Nov 26 '18 at 23:49
@Daniel. I'm confused. How would I set my directory structure up to reflect this?
– NevDull
Nov 27 '18 at 0:49
add a comment |
2
don't write one module per class. Put all your classes inapplib.
– Daniel
Nov 26 '18 at 23:49
1
"Each class is contained within its own file of the same name" - bad idea. It causes all sorts of confusion, including mixing up classes and modules, and making things like circular import problems much more common.
– user2357112
Nov 26 '18 at 23:49
@Daniel. I'm confused. How would I set my directory structure up to reflect this?
– NevDull
Nov 27 '18 at 0:49
2
2
don't write one module per class. Put all your classes in
applib.– Daniel
Nov 26 '18 at 23:49
don't write one module per class. Put all your classes in
applib.– Daniel
Nov 26 '18 at 23:49
1
1
"Each class is contained within its own file of the same name" - bad idea. It causes all sorts of confusion, including mixing up classes and modules, and making things like circular import problems much more common.
– user2357112
Nov 26 '18 at 23:49
"Each class is contained within its own file of the same name" - bad idea. It causes all sorts of confusion, including mixing up classes and modules, and making things like circular import problems much more common.
– user2357112
Nov 26 '18 at 23:49
@Daniel. I'm confused. How would I set my directory structure up to reflect this?
– NevDull
Nov 27 '18 at 0:49
@Daniel. I'm confused. How would I set my directory structure up to reflect this?
– NevDull
Nov 27 '18 at 0:49
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f53490773%2favoiding-duplication-of-namespace-elements-in-python-imports%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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%2f53490773%2favoiding-duplication-of-namespace-elements-in-python-imports%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
2
don't write one module per class. Put all your classes in
applib.– Daniel
Nov 26 '18 at 23:49
1
"Each class is contained within its own file of the same name" - bad idea. It causes all sorts of confusion, including mixing up classes and modules, and making things like circular import problems much more common.
– user2357112
Nov 26 '18 at 23:49
@Daniel. I'm confused. How would I set my directory structure up to reflect this?
– NevDull
Nov 27 '18 at 0:49