-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
DOC: Make explicit in pandas IO doc the imports and options #28089
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
10 commits
Select commit
Hold shift + click to select a range
5e0fbe3
DOC: Make explicit in pandas IO doc the iports and options
TanyaaCJain 3591894
Merge branch 'master' of https://github.com/pandas-dev/pandas
TanyaaCJain 035e35b
Merge branch 'master' of https://github.com/pandas-dev/pandas into do…
TanyaaCJain 18a9b7c
DOC: Update io.rst to explicitly add imports and options
TanyaaCJain 1ff8b3f
Merge branch 'master' of https://github.com/pandas-dev/pandas into do…
TanyaaCJain d3036f3
DOC: Removed pandas row display option because it is not required at …
TanyaaCJain 37d420a
Merge branch 'master' of https://github.com/pandas-dev/pandas into do…
TanyaaCJain f80331e
DOC: Remove unused clipdf assignment, numpy print options and seed
TanyaaCJain faec275
Merge branch 'master' of https://github.com/pandas-dev/pandas into do…
TanyaaCJain 6487a68
DOC: Remove unused clipdf assignment, numpy print options and seed
TanyaaCJain 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
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 realize I missed the original discussion but just to be clear, is the assumption here that we only show the import the first time it shows up one of the rst files and that the rest of the code blocks use it from there?
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 don't think that's an assumption. It is implicitly being proposed, for simplicity and for inertia on how the header worked, but it's surely open to discussion. I thought about that too, and I was also wondering if it'd make sense to split the long pages we have now in the user guide in shorter pages. I guess that could make things easier if we finally make the code runnable.