Skip to content

Backport PR #52400 on branch 2.0.x (DOC: Typo: Fix inline code block to use double quotes instead of triple quotes) #52416

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.

Sign up for GitHub

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 1 commit into from
Apr 4, 2023
+1 −1
Merged

Backport PR #52400 on branch 2.0.x (DOC: Typo: Fix inline code block to use double quotes instead of triple quotes) #52416

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/source/whatsnew/v2.0.0.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ Below is a possibly non-exhaustive list of changes:
1. Instantiating using a numpy numeric array now follows the dtype of the numpy array.
Previously, all indexes created from numpy numeric arrays were forced to 64-bit. Now,
for example, ``Index(np.array([1, 2, 3]))`` will be ``int32`` on 32-bit systems, where
it previously would have been ``int64``` even on 32-bit systems.
it previously would have been ``int64`` even on 32-bit systems.
Instantiating :class:`Index` using a list of numbers will still return 64bit dtypes,
e.g. ``Index([1, 2, 3])`` will have a ``int64`` dtype, which is the same as previously.
2. The various numeric datetime attributes of :class:`DatetimeIndex` (:attr:`~DatetimeIndex.day`,
Expand Down