Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import seaborn as ?? #229

Closed
8one6 opened this issue Jun 30, 2014 · 13 comments
Closed

Import seaborn as ?? #229

8one6 opened this issue Jun 30, 2014 · 13 comments

Comments

@8one6
Copy link

8one6 commented Jun 30, 2014

Not an issue, just a question from an enthusiastic user. You seem to like

import seaborn as sns

as your import style. When you type that, what is the voice in your head saying out loud? I had generally been importing as sbn since it "sounded right".

@mwaskom
Copy link
Owner

mwaskom commented Jun 30, 2014

I just say the letters, usually.

@8one6
Copy link
Author

8one6 commented Jun 30, 2014

Hah, sorry, I should have been clearer: is sns an acronym for something? I.e. why did you pick sns and not sea or sbn or sbrn? For most packages, I understand why people picked the import conventions they picked, but this one was always a (small) mystery to me.

@mwaskom
Copy link
Owner

mwaskom commented Jun 30, 2014

Ah, it's a very inside joke that you might find funny if you get the origin of the package name :)

@8one6
Copy link
Author

8one6 commented Jun 30, 2014

Norman?

@mwaskom
Copy link
Owner

mwaskom commented Jun 30, 2014

👍

@8one6 8one6 closed this as completed Jun 30, 2014
@twiecki
Copy link

twiecki commented Jun 30, 2014

While I think that this is funny I think this should be mentioned somewhere. For code readability, module abbreviations should be consistent and I think people would more readily use sns if they knew why :).

@8one6
Copy link
Author

8one6 commented Jun 30, 2014

All kidding aside, I think that's a very reasonable point. I suppose I prefer sbn since it doesn't require people to "get the joke" even if the joke is documented. But I'm a team player, so I will probably just confirm my code to whatever consensus seems to be.

@8one6 8one6 reopened this Jun 30, 2014
@mwaskom
Copy link
Owner

mwaskom commented Jun 30, 2014

Eh, it's used very consistently throughout the docs, and anywhere I've used it on the internet (stackoverflow, gists, etc.). If people want to be nonconformist, they're not likely to be swayed otherwise by the fact that there's a silly reason behind the "official" abbreviation.

@mwaskom
Copy link
Owner

mwaskom commented Jun 30, 2014

(Also there's not really an obvious place in the docs to do it, since I don't think there's a single point of entry aside from the homepage and intro which are higher-level. Maybe on "installing and getting started"?).

@mwaskom mwaskom added the docs label Aug 2, 2014
@8one6
Copy link
Author

8one6 commented Aug 21, 2014

I think the "installing and getting started" idea is right on. Keep it an inside joke, or link to an explain. But something to the effect of "typical import syntax is import seaborn as sns".

@mwaskom
Copy link
Owner

mwaskom commented Sep 2, 2014

Closed with #265

@0Antact1
Copy link

0Antact1 commented Jun 26, 2023

Can anyone share what the joke is with sns?
Nevermind, found this within a GSearch https://stackoverflow.com/questions/41499857/why-import-seaborn-as-sns .

@vaibhav2304
Copy link

vaibhav2304 commented Aug 5, 2024

Not an issue, just a question from an enthusiastic user. You seem to like

import seaborn as sns

as your import style. When you type that, what is the voice in your head saying out loud? I had generally been importing as sbn since it "sounded right".

Official Seaborn website, "sns" can be interpreted as “Seaborn Name Space

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants