-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: pd.show_versions: json.decoder.JSONDecodeError #39766
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
alexprincel
commented
Feb 12, 2021
•
edited
Loading
edited
- [ x] closes BUG: pd.show_versions: json.decoder.JSONDecodeError #39701
- [ x] tests added / passed
- [ x] Ensure all linting tests pass, see here for how to run them
- whatsnew entry
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 @alexprincel for the PR.
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.
Can you add a note in the whatsnew?(doc/source/whatsnew/v1.3.0.rst
, I think this should go under Other in the section bug fixes.)
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.
pls also add a whatsnew note. bug fixes in I/O sectoin are ok
Hello @alexprincel! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found: There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2021-02-22 18:00:28 UTC |
Not sure if this needs commenting (again, first-timer), but I believe I have implemented all requested changes and made testing more robust. |
@alexprincel Looking at the diff, it looks like a merge went wrong somewhere. Can you fix this up? |
Sorry about that. What seems to be the problem? I will do my best to resolve it. My git skills are not yet up to par. |
@alexprincel If you click on |
I saw this as well after. I have been reading on git this week and trying some things on test repos just to understand exactly what I need to do to correct this. If I can't figure it out I'll just start a new branch, put the modified files in that branch's working directory and commit that. |
If you only need to revert a handful of files, I'd suggest git remote -v # check that `upstream` is pandas-dev/pandas and `origin` is alexprincel/pandas
git fetch upstream master
git checkout upstream/master -- pandas/tests/io
git commit -m 'revert unrelated changes'
git push origin alexdev |
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 @alexprincel for updating - I think this almost ready, just a couple of minor comments
Will make them later today. Thanks for your comments, helps me improve. |
I have addressed all comments. Thanks ! |
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 @alexprincel - just one unused function to remove, other than that this looks good to me
Co-authored-by: Marco Gorelli <[email protected]>
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.
Pending green, this looks good to me
@simonjayhawkins any further comments, or good to merge?
LGTM |
cool - merging then, as commit Thank you @alexprincel ! |
Thank you for your patience on this! Hopefully I will be more efficient on my next PR. |