-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
ENH: Add orient=tight format for dictionaries #35292
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
Merged
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
bed9772
Add orient=tight format for dictionaries
Dr-Irv 520f9c5
fix up documentation formatting
Dr-Irv e46d5ac
code formatting in docs
Dr-Irv 06c3f2a
fix indentation in docstrings
Dr-Irv d8e68f9
add period to docstring for from_dict orient
Dr-Irv 1ef32fc
add blank line in docstring
Dr-Irv 344687f
Merge branch 'master' into issue4889
Dr-Irv f7998d3
WIP on adding to_dict
Dr-Irv 038eff5
Merge with master
Dr-Irv 77fec12
change versionchanged to 1.4.0. Fix typing issue, update API calls
Dr-Irv dace93d
Merge branch 'master' into issue4889
Dr-Irv File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 ensure_index does this
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.
@Dr-Irv can you review this comment here
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.
@jreback
ensure_index
doesn't handle the names of the indexes (or columns), so you'd still have logic to handle that part anyway.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.
does this work
e..g just use
Index
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.
No, because note that the argument to set the names of a
MultiIndex
isnames
, while for anIndex
it isname
. In your example in cell 99, you lost the name of the index.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.
grr this is a bug, actually is this still true on master (this was a pretty old version i am using)
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.
Still an issue. Using
pd.Index
, withnames
, you get aFutureWarning
. Withname
, you get a stack trace.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.
nvm we removed
names=
. i still find this a bit of a footgun.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.
ok i think we need to handle this a bit bitter if you wouldn't mind opening an issue.
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.
@jreback Seems like we ought to have another issue with respect to
pd.Index([(1,0), (1,1)], name=["foo", "bar"])
not returning aMultiIndex
??