-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
TST: Added test for json containing the key "last_status_change_at" #34169
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
TST: Added test for json containing the key "last_status_change_at" #34169
Conversation
Added test for issue pandas-dev#32409, json containing dicts containing the key last_status_change_at
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.
Could you move this test to pandas/tests/frame/methods/test_describe.py
?
And structure the test similar to what is describe in our guide?
https://pandas.pydata.org/pandas-docs/stable/development/contributing.html#writing-tests
|
||
|
||
def test__unhashable_dict(): | ||
result = pd.DataFrame( |
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.
- Could you remove the extra
_
intest__
- Could you add the issue number as a comment?
- This test should test this behavior: pandas1.0.1 has trouble with certain column names #32409 (comment)
@rivera-fernando can you merge master and respond to comments |
|
||
def test_unhashable_dict(): | ||
# GH#32409 | ||
result = pd.DataFrame( |
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.
Thanks @rivera-fernando
What's the difference between result
and expected? Can you construct result
using .describe
(as in the original issue)?
closing as stale |
black pandas
git diff upstream/master -u -- "*.py" | flake8 --diff