-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
e.g.
and i.e.
look nicer than eg
and ie
#3748
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
Conversation
Didn't we do a massive amount of work recently to standardize the other way? |
I'm terribly sorry. I should have asked before doing anything. |
@yuvallanger No worries, I'm sorry you did a bunch of redundent work! See: #1916 (original issues #1423) and we standardized on 'e.g.'. I suspect that is the reason that the PR won't merge cleanly. |
Could probably use similar work for things like "ie" to "i.e." On Sat, Nov 1, 2014 at 11:26 AM, Thomas A Caswell notifications@github.com
|
@tacaswell The reason is that I used v1.0.x-maint as the guidelines suggested. @WeatherGod said I should ask for a pull request into v1.4.x instead, but I forgot I used v1.0.x-maint as my.. hmm.. what is the technically correct term here? Source branch? Base branch? Anyways, it's my fault alone. |
I would suggest checking out the latest branch (either 1.4.x or master, lean towards v1.4.x) and re-run that command. And where do the docs suggest working against 1.0.x-maint? That should not there (that branch was last touched in 2011)... |
CONTRIBUTING.md leads to: http://matplotlib.org/devel/coding_guide.html where it says: I figured that means I should PR into the branch saying |
Ah, fair enough. That documentation should be clarified and the old branches should probably be removed. I would strongly suggest working off of 1.4.x (which is now the 'maintenance branch') as other PRs could have changed the same doc strings between now and where ever you base you edits from which will result is (really hard to resolve) conflicts when we try to merge the changes into 1.4.x. |
Used: ```bash find * -type f -exec sed -i 's/\beg,/e.g.,/g' {} \; ```
d85b990
to
03e6f11
Compare
Used: ```bash find * -type f -exec sed -i 's/\beg\b/e.g.,/g' {} \; ```
03e6f11
to
ef80b70
Compare
That's it. I hope you like it. I don't know much about style guidelines, so I won't change anything further. I should probably use this same PR for the |
Used: ```bash find * -type f -exec sed -i 's/\bie,/i.e.,/g' {} \; ```
e.g.
looks nicer than eg
e.g.
and i.e.
look nicer than eg
and ie
Adding the dots apparently made one of the lines too long, can you please fix that? |
@@ -5420,7 +5420,7 @@ def hist(self, x, bins=10, range=None, normed=False, weights=None, | |||
normed : boolean, optional, default: False | |||
If `True`, the first element of the return tuple will | |||
be the counts normalized to form a probability density, i.e., | |||
``n/(len(x)`dbin)``, ie the integral of the histogram will sum to | |||
``n/(len(x)`dbin)``, i.e., the integral of the histogram will sum to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the line that is now too long.
Used: ```bash find * -type f -exec sed -i 's/\bie\b/i.e.,/g' {} \; ``` Restructuring >80 character docstring
546466b
to
2213ac8
Compare
DOC : `e.g.` and `i.e.` look nicer than `eg` and `ie`
Thanks! Congratulations on your first mpl commits (I think). |
Adding many more
eg
toe.g.
replacements.I ran:
and then manually filtered for errors.