-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
CLN: res/exp and GH references in frame tests #22730
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
Changes from all commits
f699cd2
e903579
be4605d
a399489
b403a73
fa0fc2f
f56bfde
f29a839
780dd84
0e70a30
855a186
733b889
d0c6d37
ca36942
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -192,7 +192,7 @@ def test_iteritems(self): | |
assert isinstance(v, self.klass._constructor_sliced) | ||
|
||
def test_items(self): | ||
# issue #17213, #13918 | ||
# GH 17213, GH 13918 | ||
cols = ['a', 'b', 'c'] | ||
df = DataFrame([[1, 2, 3], [4, 5, 6]], columns=cols) | ||
for c, (k, v) in zip(cols, df.items()): | ||
|
@@ -213,7 +213,7 @@ def test_iterrows(self, float_frame, float_string_frame): | |
self._assert_series_equal(v, exp) | ||
|
||
def test_iterrows_iso8601(self): | ||
# GH19671 | ||
# GH 19671 | ||
if self.klass == SparseDataFrame: | ||
pytest.xfail(reason='SparseBlock datetime type not implemented.') | ||
|
||
|
@@ -354,7 +354,7 @@ def test_axis_aliases(self, float_frame): | |
assert_series_equal(result, expected) | ||
|
||
def test_class_axis(self): | ||
# https://github.com/pandas-dev/pandas/issues/18147 | ||
# GH 18147 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Generally still ask that you try to minimize your changes as much as possible. Obviously changing comments isn't going to affect any of the code base but it still makes the diffs of your PRs unnecessarily larger, which makes reviews more difficult. You should always look for logical separation points for smaller PRs, i.e. if you really want to clean up these comments then make a separate PR for that rather than bundling here. For this change please revert this file to master There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. IMO these are trivial changes that don't get done otherwise, and what's more I did get asked to do this in several PRs, so I just do it preemptively. However, I separated the commits between fixturizing and import-cleaning, so you can review the separate commits (almost) as separate PRs. |
||
# no exception and no empty docstring | ||
assert pydoc.getdoc(DataFrame.index) | ||
assert pydoc.getdoc(DataFrame.columns) | ||
|
@@ -366,9 +366,9 @@ def test_more_values(self, float_string_frame): | |
def test_repr_with_mi_nat(self, float_string_frame): | ||
df = self.klass({'X': [1, 2]}, | ||
index=[[pd.NaT, pd.Timestamp('20130101')], ['a', 'b']]) | ||
res = repr(df) | ||
exp = ' X\nNaT a 1\n2013-01-01 b 2' | ||
assert res == exp | ||
result = repr(df) | ||
expected = ' X\nNaT a 1\n2013-01-01 b 2' | ||
assert result == expected | ||
|
||
def test_iteritems_names(self, float_string_frame): | ||
for k, v in compat.iteritems(float_string_frame): | ||
|
@@ -418,7 +418,7 @@ def test_values(self, float_frame): | |
assert (float_frame.values[:, 0] == 5).all() | ||
|
||
def test_as_matrix_deprecated(self, float_frame): | ||
# GH18458 | ||
# GH 18458 | ||
with tm.assert_produces_warning(FutureWarning): | ||
cols = float_frame.columns.tolist() | ||
result = float_frame.as_matrix(columns=cols) | ||
|
@@ -439,7 +439,7 @@ def test_transpose_get_view(self, float_frame): | |
assert (float_frame.values[5:10] == 5).all() | ||
|
||
def test_inplace_return_self(self): | ||
# re #1893 | ||
# GH 1893 | ||
|
||
data = DataFrame({'a': ['foo', 'bar', 'baz', 'qux'], | ||
'b': [0, 0, 1, 1], | ||
|
@@ -503,7 +503,7 @@ def _check_f(base, f): | |
_check_f(d.copy(), f) | ||
|
||
def test_tab_complete_warning(self, ip): | ||
# https://github.com/pandas-dev/pandas/issues/16409 | ||
# GH 16409 | ||
pytest.importorskip('IPython', minversion="6.0.0") | ||
from IPython.core.completer import provisionalcompleter | ||
|
||
|
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.
I think these shouldn't have spaced and instead should be gh-676 as then they show up in the viewer cc @gfyoung
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.
The
gh-*
format is standard for Git commits to GitHub, as those links get parsed. Other formats do not get that same treatment AFAIK. As for the viewer, it doesn't really matter, as I don't believe GitHub parses them inline.That being said, while my personal preference is to use
gh-*
, I'm a little unsure as to why we are trying to standardize the references given that they are somewhat moot in the viewer...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.
I chose the most common/consistent formatting. Can go to
gh-
as well...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.
@h-vetinari : Given that this really doesn't affect anything from a GitHub UI perspective, I am indifferent as to which way you go. Just making sure you're aware that what you're doing is purely aesthetic for our developer eyes. 🙂
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.
@gfyoung
Hmmm, visually I prefer
# GH 1234
over# gh-1234
. Didn't see your comment soon enough before I pushed the new commit, reverting.