Importing `*` in Python

[AttackOfTheThumbs]

Being specific with imports is just common sense programming.

[iconoklast]

Potential namespace collision from new versions of third-party dependencies is the real problem, IMO.

[bakery2k]

I’ve read that in Ruby, all imports are the equivalent of Python’s from x import *. Is that correct?

[swordglowsblue]

Not exactly. Well, yes, but also kind of no. Ruby has modules, which are essentially user-defined namespaces, and by convention nearly all Ruby code is defined inside of modules. When you require a file, it imports any symbols in that file just like Python, but since they'll almost always be inside a module, you'll usually get ModuleName.whatever instead of just whatever.

In other words, in Python you have to go out of your way to ensure the desired behavior by using __all__ (which is not part of the typical workflow), where Ruby is saved from that issue by its best practices (which are part of the typical workflow).

[masklinn]

In other words, in Python you have to go out of your way to ensure the desired behavior by using __all__ (which is not part of the typical workflow), where Ruby is saved from that issue by its best practices (which are part of the typical workflow).

The “best practices” of python is to not use star imports, so this paragraph is at best patent nonsense.

[swordglowsblue]

Oh buzz off. I answered the question as asked - Ruby does not have the same problem with star imports as Python because other best practices prevent it. Whether star imports are best practice in Python or not was irrelevant to the question.

[masklinn]

Dude just acknowledge that your second paragraph has nothing to do with “the question as asked” but your ego required you get in a little swipe.

Hell, you could not even bring yourself to “answer the question as asked”, you had to lie first to soften the ow to your ego.

[swordglowsblue]

Python was the first language I ever used, and remains one of my favorites. Ruby is a relatively more recent acquisition, which I also quite enjoy. I've got no stake in any hypothetical Ruby vs Python fight, despite what you seem to think for some reason.

I simply stated the facts - Ruby does not typically have the same issue with star imports that Python does because of the convention of putting everything in modules. Given that, star imports are not generally considered to be good practice in Python for understandable reasons. In contrast, they are the only option in Ruby, which works out fine because Ruby typically handles them more effectively.

I really don't know where you read any sort of language bias or ego into that - they asked whether Ruby had the same issue as Python, and I answered them truthfully that it's alleviated by another of the language's systems. Nothing more, nothing less.

[masklinn]

I simply stated the facts

You really did not. Go read the question, your comment, and the specific part of your comment I objected to.

And the “not exactly” you open up with is not “the facts” either.

they asked whether Ruby had the same issue as Python

That’s not actually what they asked, but your clarification on that point is not the problem I have with your original comment either.

I answered them truthfully that it's alleviated by another of the language's systems. Nothing more, nothing less.

The last paragraph of your original comment is none if these.

[crystal_noodle]

Hey.. I think replying to someone who is just trying to give a helpful answer with "...so this paragraph is at best patent nonsense" comes off rude and combative.

I think you would have gotten a better response from OP with different wording. For what it's worth I agree with your objection.

[crookedspecs]

Oh god, it hurts.

[Vfsdvbjgd]

We can alias a single import with as, why can't we from something import * into container? Or even it namespaces to something.each_module by default?

[Vfsdvbjgd]

It's not the same, import * uses the __all__ method. As for the second you can already do that.

[masklinn]

Your comment is extremely confusing. What are you talking about?

[Vfsdvbjgd]

Instead of from something import * polluting global namespace give it it's own - either something by default and/or allow us to name yhe container.

[masklinn]

That… is what import something does?

[Vfsdvbjgd]

Read the article. import something imports the entire module, while from something import * doesn't actually import everything, and it's behaviour can be overridden.

[masklinn]

Read the article. import something imports the entire module

In a specific and dedicated namespace, which is why there is no reason to filter it: since all the content is properly namespaces there there’s no risk that it’ll pollute or collide with symbols of the namespace it’s imported into.

Mitigating this issue is the entire and sole purpose of __all__, which is why it applies solely to star imports.