-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Comments
I just say the letters, usually. |
Hah, sorry, I should have been clearer: is |
Ah, it's a very inside joke that you might find funny if you get the origin of the package name :) |
Norman? |
👍 |
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 |
All kidding aside, I think that's a very reasonable point. I suppose I prefer |
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. |
(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"?). |
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 |
Closed with #265 |
Can anyone share what the joke is with sns? |
Official Seaborn website, "sns" can be interpreted as “Seaborn Name Space |
Not an issue, just a question from an enthusiastic user. You seem to like
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".The text was updated successfully, but these errors were encountered: